web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / PCF - NPM START WATCH ...
Power Apps
Answered

PCF - NPM START WATCH Erroring Out with [8:13:25 pm] [start] [watch] Failed: [pcf-1006] [Error] pcf-start exited with code 1

(0) ShareShare
ReportReport
Posted on by

Hi All,

 

I am trying to test my PCF control using the npm start watch / npm start command but its erroring out with below :

PS C:\Users\SASHI\PCFPractice> npm start watch

> pcf-project@1.0.0 start C:\Users\SASHI\PCFPractice
> pcf-scripts start "watch"

[8:13:22 pm] [start] [watch] Initializing...
[8:13:22 pm] [start] [watch] Validating manifest...
[8:13:22 pm] [start] [watch] Validating control...
[8:13:23 pm] [start] [watch] Generating manifest types...
[8:13:23 pm] [start] [watch] Generating design types...
[8:13:23 pm] [start] [watch] Compiling and bundling control...
[Webpack stats]:
Hash: 0853940db24eb6c2e5df
Version: webpack 4.42.1
Time: 1334ms
Built at: 18/06/2021 8:13:25 pm
Asset Size Chunks Chunk Names
bundle.js 7.33 KiB main [emitted] main
Entrypoint main = bundle.js
[./MyPCFControl/index.ts] 3.29 KiB {main} [built]
[8:13:25 pm] [start] [watch] Generating build outputs...
[8:13:25 pm] [start] [watch] Starting control harness...
internal/modules/cjs/loader.js:443
throw e;
^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './v4' is not defined by "exports" in C:\Users\SASHI\PCFPractice\node_modules\pcf-start\node_modules\uuid\package.json
at throwExportsNotFound (internal/modules/esm/resolve.js:290:9)
at packageExportsResolve (internal/modules/esm/resolve.js:513:3)
at resolveExports (internal/modules/cjs/loader.js:437:36)
at Function.Module._findPath (internal/modules/cjs/loader.js:477:31)
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:872:27)
at Function.Module._load (internal/modules/cjs/loader.js:730:27)
at Module.require (internal/modules/cjs/loader.js:957:19)
at Module.patchedRequire [as require] (C:\Users\SASHI\PCFPractice\node_modules\diagnostic-channel\dist\src\patchRequire.js:14:46)
at require (internal/modules/cjs/helpers.js:88:18)
at Object.<anonymous> (C:\Users\SASHI\PCFPractice\node_modules\pcf-start\generated\localfileusersettings.js:9:14)
{
code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

[8:13:25 pm] [start] [watch] Failed:
[pcf-1006] [Error] pcf-start exited with code 1
(node:18268) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'compileTime' of undefined
at C:\Users\SASHI\PCFPractice\node_modules\pcf-scripts\bin\pcf-scripts.js:67:42
at Generator.next (<anonymous>)
at fulfilled (C:\Users\SASHI\PCFPractice\node_modules\pcf-scripts\bin\pcf-scripts.js:7:58)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:18268) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:18268) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

 

As Part of troubleshooting I tried :

Run NPM Install ---- Didn't Work 

rollbacked the version of PowerApps CLI version -- Run npm install ----Build the PCF control --- Run npm start ---- Still it didn't work and gave me the same error .

 

Any Assistance or Help  is highly appreciated.

 

 

I have the same question (0)
  • Verified answer
    Diana Birkelbach Profile Picture
    3,072 Most Valuable Professional on at

    Hi @Sashi , 

     

    It's a known issue with the pac cli 1.7.2.

    Try using an older version of the pcf-start:

    npm install pcf-start@1.6.5

    After that, using "npm list" you shoudn't see "uuid" version 8.3.2 in the list anymore.

     

    You would need to revert this change when a new "pac cli" will be available, by using: 

    npm install pcf-start@latest


    Hope it helps!

    Diana

     

  • Hemant Gaur Profile Picture
    Microsoft Employee on at

    This should be fixed with the latest update on the pac CLI which has the hotfix for this issue 

    >> pac install latest

    >> pac use latest

    1.7.3 (Latest)

     

    revert if you have made change to package.json for pcf-start 

        "pcf-start""^1"

     

    >> npm install pcf-start@latest

    Let me know if there are any questions. 

    Thanks,

    Hemant 

  • yusuffbasha Profile Picture
    4 on at

    Hi Diana,

     

    My pac cli version is 1.9.4

    The solution is not working in my case. Showing the same error after installing pcf-start@1.6.5 

     

  • Diana Birkelbach Profile Picture
    3,072 Most Valuable Professional on at

    Hi @yusuffbasha , 

    With 1.9.4 should work.

    Is it exactly the same error message as above, containing "Package subpath './v4' is not defined by "exports" in"?

    Lately there are some issues with the typescript dependecy, so maybe it's another issue?

     

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
11manish Profile Picture

11manish 530

#2
WarrenBelz Profile Picture

WarrenBelz 459 Most Valuable Professional

#3
Haque Profile Picture

Haque 314

Last 30 days Overall leaderboard