npm ERR! error:0906D06C:PEM routines:PEM_read_bio:no start line

OS: Windows 10 Pro
Node: v9.5.0
npm: 6.5.0

So, changing my package file script from:

"dev": "set NODE_ENV=development&&node server.js"

to

"dev": "set NODE_ENV=development&&npx supervisor server.js"

and running npm run dev causes the above mentioned error to be issued. What is the issue here?

The full error log is as follows:

npm ERR! error:0906D06C:PEM routines:PEM_read_bio:no start line

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\d0475\AppData\Roaming\npm-cache\_logs\2019-06-11T09_39_11_946Z-debug.log
Install for prefix@latest failed with code 1
npx: installed 1 in 5.556s
C:\Users\d0475\AppData\Roaming\npm-cache\_npx\10568\node_modules\supervisor\lib\cli-wrapper.js

Running node-supervisor with
  program 'server.js'
  --watch '.'
  --extensions 'node,js'
  --exec 'node'

Starting child process with 'node server.js'
Watching directory 'C:\Users\d0475\Documents\Projects\flamingo-ecom2\sick-fits\frontend' for changes.
Press rs for restarting the process.
Parent process exiting, terminating child...
events.js:137
      throw er; // Unhandled 'error' event
      ^

Error: Error watching file for changes: EPERM
    at _errnoException (util.js:1003:13)
    at FSEvent.FSWatcher._handle.onchange (fs.js:1382:9)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! flamingo-frontend@1.0.0 dev: `set NODE_ENV=development&&npx supervisor server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the flamingo-frontend@1.0.0 dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\d0475\AppData\Roaming\npm-cache\_logs\2019-06-11T09_39_42_893Z-debug.log

Given the change you made and the error message, looks like an error with supervisor rather than npm.

(Because this forum is focused on npm, you might want to ask your question somewhere that targets experts with your package.)

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.