An error occurred while running subprocess npm

Issue

An error occurs when I try to start a new ionic project

I’ve tried to reinstall npm, node, ionic, clean npm cache
npm cache verify]
npm cache clean –force

Error code:

npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm ERR! Unexpected token : in JSON at position 260218 while parsing near '...RA9TVsSAnZWagAAGRgm":"d262c5b83aa5cf4386...'

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Lucas\AppData\Roaming\npm-cache\_logs\2021-04-30T23_24_15_632Z-debug.log
[ERROR] An error occurred while running subprocess npm.

        npm.cmd i exited with exit code 1.

        Re-running this command with the --verbose flag may provide more information.

log:

4108 verbose Windows_NT 10.0.21370 4109 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "i" 4110 verbose node v14.16.1 4111 verbose npm v6.14.12 4112 error Unexpected token : in JSON at position 260218 while parsing near '...RA9TVsSAnZWagAAGRgm":"d262c5b83aa5cf4386...' 4113 verbose exit [ 1, true ]

Solution

You have the answer right in the logs that you have posted.

npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

And

verbose node v14.16.1 4111 

Downgrade to a version of node less than 14 by either uninstalling your current version or using nvm. Personally I like using nmv.

Answered By – E. Maggini

This Answer collected from stackoverflow, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply

(*) Required, Your email will not be published