I am trying to get my project started but I got this error.
Error from Terminal
The environment requires npm 6.x or lower. I checked with Terminal and it does satisfy the required version.
my npm version
I had once installed node v16 using the official installer before but soon I uninstalled it by following the steps I googled (like sudo rm all node-related stuff).
What I had done includes the following:
Clear Cache, Remove package-lock.json, Remove node_modules, and reinstall - not working
rm all the node-related files and reinstall node (v14) - not working
use nvm to run - not working
Here is the debug log I got from npm:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/Users/.nvm/versions/node/v12.22.12/bin/node',
1 verbose cli '/Users/.nvm/versions/node/v12.22.12/bin/npm',
1 verbose cli 'run',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm#6.14.16
3 info using node#v12.22.12
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle sentry_fe#1.0.0~prestart: sentry_fe#1.0.0
6 info lifecycle sentry_fe#1.0.0~start: sentry_fe#1.0.0
7 verbose lifecycle sentry_fe#1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle sentry_fe#1.0.0~start: PATH: /Users/.nvm/versions/node/v12.22.12/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/Documents/WORK/governance-sentry-fe/node_modules/.bin:/Users/.nvm/versions/node/v12.22.12/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/puppetlabs/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin
9 verbose lifecycle sentry_fe#1.0.0~start: CWD: /Users/Documents/WORK/governance-sentry-fe
10 silly lifecycle sentry_fe#1.0.0~start: Args: [ '-c', 'eden start' ]
11 silly lifecycle sentry_fe#1.0.0~start: Returned: code: 1 signal: null
12 info lifecycle sentry_fe#1.0.0~start: Failed to exec start script
13 verbose stack Error: sentry_fe#1.0.0 start: `eden start`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/Users/.nvm/versions/node/v12.22.12/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess.<anonymous> (/Users/.nvm/versions/node/v12.22.12/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1022:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid sentry_fe#1.0.0
15 verbose cwd /Users/Documents/WORK/governance-sentry-fe
16 verbose Darwin 21.3.0
17 verbose argv "/Users/.nvm/versions/node/v12.22.12/bin/node" "/Users/.nvm/versions/node/v12.22.12/bin/npm" "run" "start"
18 verbose node v12.22.12
19 verbose npm v6.14.16
20 error code ELIFECYCLE
21 error errno 1
22 error sentry_fe#1.0.0 start: `eden start`
22 error Exit status 1
23 error Failed at the sentry_fe#1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Would any one imply other methods that I can use? Any responses would be appreciated.
I'm not sure if I understand your question, but I'll try my best to answer.
You can reinstall the latest version of Node.js from the official website (it should remove the old version).
This should also install npm at version 8.
To downgrade npm, you need to run the following command.
$ npm install -g npm#6.14.16
This should leave Node.js at the highest version, and npm at your desired version.
install n;
npm install -g n
or without node on mac;
brew install n
after installation execute;
n 16.15.1
if you want other versions;
n <version>
or you can install last via;
n latest
i advise for new developers;
n lts
also you can switch installed versions via
n
For more info...
Related
I've received the following in the debug log. I'm looking to npx create-react-app. The terminal is returning
npm ERR! cb.apply is not a function
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User\AppData\Roaming\npm-cache_logs\2022-06-07T14_57_21_064Z-debug.log
Install for [ 'create-react-app#latest' ] failed with code 1
This is the debug file...
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files (x86)\\Nodist\\v-x64\\18.1.0\\node.exe',
1 verbose cli 'C:\\Program Files (x86)\\Nodist\\bin\\node_modules\\npx\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'create-react-app#latest',
1 verbose cli '--global',
1 verbose cli '--prefix',
1 verbose cli 'C:\\Users\\User\\AppData\\Roaming\\npm-cache\\_npx\\50292',
1 verbose cli '--loglevel',
1 verbose cli 'error',
1 verbose cli '--json'
1 verbose cli ]
2 info using npm#5.1.0
3 info using node#v18.1.0
4 verbose npm-session 56a59e1a77678c6d
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 200 https://registry.npmjs.org/create-react-app 102ms (from cache)
8 silly pacote tag manifest for create-react-app#latest fetched in 165ms
9 verbose stack TypeError: cb.apply is not a function
9 verbose stack at C:\Program Files (x86)\Nodist\bin\node_modules\npx\node_modules\npm\node_modules\graceful-fs\polyfills.js:287:18
9 verbose stack at FSReqCallback.oncomplete (node:fs:204:5)
10 verbose cwd C:\Users\User\Websites\react
11 verbose Windows_NT 10.0.19044
12 verbose argv "C:\\Program Files (x86)\\Nodist\\v-x64\\18.1.0\\node.exe" "C:\\Program Files (x86)\\Nodist\\bin\\node_modules\\npx\\node_modules\\npm\\bin\\npm-cli.js" "install" "create-react-app#latest" "--global" "--prefix" "C:\\Users\\User\\AppData\\Roaming\\npm-cache\\_npx\\50292" "--loglevel" "error" "--json"
13 verbose node v18.1.0
14 verbose npm v5.1.0
15 error cb.apply is not a function
16 verbose exit [ 1, true ]
I'm using the latest beta version of Node, so I'll try to go back to the latest stable version. If that doesn't work, I'll try to re-download node away from nodist..
If you have any other thoughts or suggestions Perhaps there is a hint in the debug log, then I'd be glad to hear them.
According to the discussion under github https://github.com/facebook/create-react-app/discussions/10173#discussioncomment-142156
you need to
npm rm -g create-react-app
npm install create-react-app
npx create-react-app my-app
After deleting the Nodist version manager. I installed nvm and I'm now able to get npx to work without a problem. I think the issue for me was that I was using the nodist version manager.
Highly recommend checking out nvm here if you get similar issues.
https://github.com/coreybutler/nvm-windows/wiki
I have installed Node.js from upgrade/install packages without any problems, but when I try to run the following: /opt/plesk/node/12/bin/node -v the output i get is:
12.4.0
The problem is that when I try to install authentication with Bootstrap for Laravel, and I get to the point where I need to run: npm install && npm run dev I get the following error when running /opt/plesk/node/12/bin/npm run dev:
Error: You are using an unspported version of Node. Please update to
at least Node v12.14
It seems like I a'm running the newest version, but it still complaints about wrong version number? - How to fix?
UPDATE (debug log):
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/opt/plesk/node/12/bin/node',
1 verbose cli '/opt/plesk/node/12/bin/npm',
1 verbose cli 'run',
1 verbose cli 'dev'
1 verbose cli ]
2 info using npm#6.9.0
3 info using node#v12.4.0
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle #~predev: #
6 info lifecycle #~dev: #
7 verbose lifecycle #~dev: unsafe-perm in lifecycle true
8 verbose lifecycle #~dev: PATH: /opt/plesk/node/12/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/www/vhosts/domain.com/httpdocs2/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/us$
9 verbose lifecycle #~dev: CWD: /var/www/vhosts/domain.com/httpdocs2
10 silly lifecycle #~dev: Args: [ '-c', 'npm run development' ]
11 silly lifecycle #~dev: Returned: code: 1 signal: null
12 info lifecycle #~dev: Failed to exec dev script
13 verbose stack Error: # dev: `npm run development`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/opt/plesk/node/12/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:200:13)
13 verbose stack at ChildProcess.<anonymous> (/opt/plesk/node/12/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:200:13)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid #
15 verbose cwd /var/www/vhosts/domain.com/httpdocs2
16 verbose Linux 4.15.0-126-generic
17 verbose argv "/opt/plesk/node/12/bin/node" "/opt/plesk/node/12/bin/npm" "run" "dev"
18 verbose node v12.4.0
19 verbose npm v6.9.0
20 error code ELIFECYCLE
21 error errno 1
22 error # dev: `npm run development`
22 error Exit status 1
23 error Failed at the # dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
A big thanks to NullDev for leading me in the right direction!
I found the answer here: How to add a new node.js version for the Node.js Manager on Plesk?
We need to install Node Version Manager
Then install whatever version we want (I wanted the newest one v14.15.4)
We then copy that version to Plesk default Node versions path
And finally we tell Plesk about the newly version created
Then in the list of all versions installed, we refresh and voila, we now have support for v14.15.4
Credit for this goes to Maertz
I'm running ubuntu on Virtual Machine on a windows computer; I have node.js and npm installed globally (node version 10.6.0; npm version 6.4.1). I cloned a React app from our internal bitbucket repo, checked out to a branch and created a new branch from that; the app is supposed to run by 'npm run dev' but when I try to run it, I get the following error:
internal/modules/cjs/loader.js:583
throw err;
^
Error: Cannot find module 'braces'
When I install module 'braces', and try 'npm run dev' it gives missing module of some other module and so on. I was told by one of the developers that I need to be running npm locally and not globally (which is how I have it in my case); I tried uninstalling node.js and npm but the system won't uninstall it. Do i need to do the uninstall from root (by doing sudo -i, going to root and uninstalling)? Also, I need node.js version 10.6.0 and npm version 6.4.1 which is needed to run my other node.js/graphQL APIs - how do I make sure that I install those exact versions, after uninstalling node.js and npm from root?
Following is debug info from debug log:
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'dev'
]
2 info using npm#6.4.1
3 info using node#v10.6.0
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle abcms#1.0.2~predev: abcms#1.0.2
6 info lifecycle abcms#1.0.2~dev: abcms#1.0.2
7 verbose lifecycle abcms#1.0.2~dev: unsafe-perm in lifecycle true
8 verbose lifecycle abcms#1.0.2~dev: PATH:
/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-
bin:/home/usname123/Documents/DEV/uppperFolder/
abcms/node_modules/.bin:/home/rv7
94a/bin:/usr/local/bin:/usr/bin:/usr/bin/js:/home/usname123/.local/
bin:/home/usn
ame123/bin:/home/usname123/.local/bin:/var/opt/SoapUI-
5.2.1/bin:/var/opt/java/jdk1.8.0_77/bin:/usr/
local/sbin:/usr/local/bin:/usr/sbin
:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle abcms#1.0.2~dev: CWD:
/home/rv794a/Documents/DEV/upperFolder/abcms
10 silly lifecycle abcms#1.0.2~dev: Args:
[ '-c', 'webpack-dev-server --
mode development --open' ]
11 silly lifecycle abcms#1.0.2~dev: Returned: code: 1 signal: null
12 info lifecycle abcms#1.0.2~dev: Failed to exec dev script
13 verbose stack Error: abcms#1.0.2 dev: `webpack-dev-server --mode
development --open`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous>
(/usr/local/lib/node_modules/npm/node_modules/npm-
lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:182:13)
13 verbose stack at ChildProcess.<anonymous>
(/usr/local/lib/node_modules/npm/node_modules/npm-
lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:182:13)
13 verbose stack at maybeClose (internal/child_process.js:961:16)
13 verbose stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:248:5)
14 verbose pkgid abcms#1.0.2
15 verbose cwd /home/usname123/Documents/DEV/upperFolder/abcms
16 verbose Linux 4.4.0-159-generic
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "dev"
18 verbose node v10.6.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error abcms#1.0.2 dev: `webpack-dev-server --mode development --open`
22 error Exit status 1
23 error Failed at the abcms#1.0.2 dev script.
23 error This is probably not a problem with npm. There is likely
additional logging output above.
24 verbose exit [ 1, true ]
I installed the latest version of node and electron and tried out the samples. They work when I enter "npm start".
However: when I try to make an app in another folder and launch it, I get this npm-debug.log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm#3.10.10
3 info using node#v6.11.2
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle proton-template-app#1.0.0~prestart: proton-template-app#1.0.0
6 silly lifecycle proton-template-app#1.0.0~prestart: no script for prestart, continuing
7 info lifecycle proton-template-app#1.0.0~start: proton-template-app#1.0.0
8 verbose lifecycle proton-template-app#1.0.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle proton-template-app#1.0.0~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/erik/Projects/Electron/tmp2/node_modules/.bin:/home/erik/bin:/home/erik/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
10 verbose lifecycle proton-template-app#1.0.0~start: CWD: /home/erik/Projects/Electron/tmp2
11 silly lifecycle proton-template-app#1.0.0~start: Args: [ '-c', 'electron .' ]
12 info lifecycle proton-template-app#1.0.0~start: Failed to exec start script
13 verbose stack Error: proton-template-app#1.0.0 start: `electron .`
13 verbose stack spawn ENOENT
13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:33:16)
13 verbose stack at emitTwo (events.js:106:13)
13 verbose stack at ChildProcess.emit (events.js:191:7)
13 verbose stack at maybeClose (internal/child_process.js:891:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
14 verbose pkgid proton-template-app#1.0.0
15 verbose cwd /home/erik/Projects/Electron/tmp2
16 error Linux 4.4.0-79-generic
17 error argv "/usr/bin/node" "/usr/bin/npm" "start"
18 error node v6.11.2
19 error npm v3.10.10
20 error file sh
21 error code ELIFECYCLE
22 error errno ENOENT
23 error syscall spawn
24 error proton-template-app#1.0.0 start: `electron .`
24 error spawn ENOENT
25 error Failed at the proton-template-app#1.0.0 start script 'electron .'.
25 error Make sure you have the latest version of node.js and npm installed.
25 error If you do, this is most likely a problem with the proton-template-app package,
25 error not with npm itself.
25 error Tell the author that this fails on your system:
25 error electron .
25 error You can get information on how to open an issue for this project with:
25 error npm bugs proton-template-app
25 error Or if that isn't available, you can get their info via:
25 error npm owner ls proton-template-app
25 error There is likely additional logging output above.
26 verbose exit [ 1, true ]
I'm afraid my install wasn't 100% ok, what should I do? Install again? How do I uninstall correctly? - I'm stuck, please help ;-)
The technicality is in your package.json, and your installation of Electron, but this is regardless of having it saved under dependencies.
If your start script in package.json calls electron ., you will need to install Electron globally with npm install electron -g. This goes for all commands where you use the name, much like mocha and cordova create. Just some examples.
To use it locally (non-globally) and only inside the project, you can just call npm install electron (which you may have done), but your startscript will have to point to the electron file inside the local node_modules folder. Usually the path is node_modules/.bin/electron.cmd, and your start script can look like node_modules/.bin/electron .
If you ever come across this problem inside an IDE, you should set electron.cmd in .bin as your executable, then . as your arguments.
Make sure you have installed electron globally, to do so run the following command:
npm install -g electron
Once you have installed it try running electron in your command prompt it should open a demo app.
To uninstall electron from the global scope:
npm uninstall -g electron
I am running BoUoW in elevation mode and have installed #angular/cli and created a sample project using the new command.
When i try to run the app by npm start it fails by stating the error ng serve failed, and blames it on npm and node version issues or the app itself. npm and node version are the latest ones.
Any angular 2 expert advice or am i using the wrong boilerplate app?
Edit:
#angular/cli: 1.0.0-beta.32.3
node: 6.9.5
npm: 3.10.10
Edit 2: (error logs)
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using npm#4.1.2
3 info using node#v7.5.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle testapp#0.0.0~prestart: testapp#0.0.0
6 silly lifecycle testapp#0.0.0~prestart: no script for prestart, continuing
7 info lifecycle testapp#0.0.0~start: testapp#0.0.0
8 verbose lifecycle testapp#0.0.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle testapp#0.0.0~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/mnt/c/Users/sande/Desktop/testapp/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
10 verbose lifecycle testapp#0.0.0~start: CWD: /mnt/c/Users/sande/Desktop/testapp
11 silly lifecycle testapp#0.0.0~start: Args: [ '-c', 'ng serve' ]
12 silly lifecycle testapp#0.0.0~start: Returned: code: 1 signal: null
13 info lifecycle testapp#0.0.0~start: Failed to exec start script
14 verbose stack Error: testapp#0.0.0 start: `ng serve`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:192:7)
14 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:192:7)
14 verbose stack at maybeClose (internal/child_process.js:890:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid testapp#0.0.0
16 verbose cwd /mnt/c/Users/sande/Desktop/testapp
17 error Linux 3.4.0+
18 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
19 error node v7.5.0
20 error npm v4.1.2
21 error code ELIFECYCLE
22 error testapp#0.0.0 start: `ng serve`
22 error Exit status 1
23 error Failed at the testapp#0.0.0 start script 'ng serve'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the testapp package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error ng serve
23 error You can get information on how to open an issue for this project with:
23 error npm bugs testapp
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls testapp
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
Edit 3: Steps to reproduce
Note i am using BoUoW on 14393.693 / 14.04.5 LTS
sudo n v7.5.0
npm install -g #angular/cli
ng new my-project
cd my-project
npm start
You've older version of node and npm. Current versions are:
node - v7.5.0
nam - 4.1.2
Please upgrade and try it again.
By the way, with Angular CLI, you can just ng serve. No need to use npm start.