I'm using windows 8.1 x64 with all updates.
I was using nodejs 8.9.1 - I took an error on command "npm -v".
So I uninstalled this version and install 8.9.3. It gave me same error on the command.
And then I uninstalled 8.9.3 and clean all paths using this answer; https://stackoverflow.com/a/20711410/1143249 Then installed new version 9.3.0...
But still, I'm getting same error in all npm commands.
What am I missing? How can I solve this problem?
C:\Users\UserName\Desktop>npm -v Error: spawn C:\Program Files\nodejs\node.exe ENOENT at _errnoException (util.js:999:13) at Process.ChildProcess._handle.onexit (internal/child_process.js:201:19) at onErrorNT (internal/child_process.js:389:16) at process._tickCallback (internal/process/next_tick.js:152:19) at Function.Module.runMain (module.js:703:11) at startup (bootstrap_node.js:194:16) at bootstrap_node.js:618:3 C:\Program Files\nodejs\node_modules\npm\lib\npm.js:51 throw new Error('npm.load() required') ^ Error: npm.load() required at Object.get (C:\Program Files\nodejs\node_modules\npm\lib\npm.js:51:13) at process.errorHandler (C:\Program Files\nodejs\node_modules\npm\lib\utils\error-handler.js:205:18) at process.emit (events.js:159:13) at process._fatalException (bootstrap_node.js:387:26) 5.5.1 events.js:136 throw er; // Unhandled 'error' event ^ Error: spawn C:\Program Files\nodejs\node.exe ENOENT at _errnoException (util.js:999:13) at Process.ChildProcess._handle.onexit (internal/child_process.js:201:19) at onErrorNT (internal/child_process.js:389:16) at process._tickCallback (internal/process/next_tick.js:152:19) at Function.Module.runMain (module.js:703:11) at startup (bootstrap_node.js:194:16) at bootstrap_node.js:618:3 Update:
Everytime I uninstalled nodejs, clean/delete folders and tried these versions;
- node-v9.3.0-x64 not working
- node-v8.9.3-x64 not working
- node-v8.9.1-x64 not working
- node-v8.9.0-x64 not working
- node-v7.10.0-x64 shows version number also a small error.
Here is the output;
C:\Users\UserName\Desktop>npm -v 5.6.0 events.js:163 throw er; // Unhandled 'error' event ^ Error: spawn C:\Program Files\nodejs\node.exe ENOENT at exports._errnoException (util.js:1050:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32) at onErrorNT (internal/child_process.js:367:16) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9) at Module.runMain (module.js:607:11) at run (bootstrap_node.js:427:7) at startup (bootstrap_node.js:151:9) at bootstrap_node.js:542:3 Update:
I uninstalled Avg anti-virus protection and installed node-v6.12.3-x64.msi. Still I have problems, an example; I can't run commands like; 
7 Answers
Answers 1
The workaround is to ensure that C:\Users\{user}\AppData\Roaming\npm exists and is writable with your normal user account.
see Troubleshooting
Answers 2
Although haven't tested Node on Windows 8, I suggest you get rid of npm installation under AppData folder altogether. You can achieve this by using a Node version manager. I recommend Nodist. You can easily switch between versions as well.
With Nodist you can run the command as such:
nodist 6.2.10 One of the things I suspect is Node runtime's limited access to required files under C:/ drive - maybe something related to Windows 8. That said, you could install nodist in any drive other than C:/. Meanwhile as mentioned by @fjoe, stick with LTS versions especially v6.x.x.
Answers 3
Here are a few things to consider when picking your node.js version.
Version labelled as LTS (Long Term Support) are the releases they stand behind.
You can see a full list of versions here notice the LTS column. It is also interesting to see the versions of V8 and npm that are packaged with each.
- Node 9.* has no official LTS release.
- Node 8.* officially entered LTS on 10-31-2017 (3 months ago).
- I personally have run into problems with it.
- Node 7.* never officially released as LTS.
- Node 6.* has 2 years of official LTS releases and they are continuing to support it.
- With the most recent release on 01-02-2018.
Given this information might I recommend you try the proven long supported version 6.*
If this works then maybe hold off on version 8.* until more things get ironed out.
Other people have commented on your question about environment variables for node or npm. This is obviously not the issue as the commands are recognized and running (but they error).
Also I would recommend you follow this full uninstall guide: How to completely remove node.js from Windows
Answers 4
My coding buddy had a similar error yesterday, although on Linux.
The error was in the node_modules folder, so removing that and reinstalling node solved it for him.
That would be your node_module folder in AppData\Roaming\npm.
Answers 5
I guess the problem can be in NPM itself. try to update your NPM.
Try to use this great approach
By the way, it's great to know what npm version you have with your changes of node.js versions.
Answers 6
From the logs you provided it looks like a cache bug, because of some junk that previously exists and that is causing issues.
Open the command prompt with admin privileges and follow the below steps:
1) Clear the cache: npm cache clean --force. You can also run npm cache verify.
2) Delete node_modules folder using: rm -rf node_modules.
3) Delete any package-lock.json file.
4) Remove the .npm directory.
5) Remove following directories :
5.1) C:\Users\<username>\AppData\Roaming\npm\. 5.2) C:\Users\<username>\AppData\Roaming\npm-cache. 6) Also, Try by setting environment variables:
C:\Users\<username>\AppData\Roaming\npm;C:\Program Files\nodejs.
Type in the command line: which npm.
Maybe you did not set the system value : NODE_PATH it should point to your global module location.
7) Update to the latest npm with npm i -g npm@latest.
Hope the above trick resolve your issue.
Thanks.
Answers 7
I guess while installing Node.js it don't able to set it's environment path due to permission.
You Need to configure Node path manually into environment variables.
0 comments:
Post a Comment