I got this error when, after installing Node.js, I went to check version of npm in cmd, but I could check the version of node without problem. And now I have this error when I try to install any package for Atom. Can someone please tell me what the heck? Thanks.
Check the windows registry. Head over to regedit -> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor and check if EnableExtensions value is 1. If not, make it 1.
I was also having the same issue and that helped me resolve it.
Related
I'm trying to create a new NextJS app, but the command npx create-next-app <name> never ends. It installs a few files along the way (including node_modules/), then after a while, among all the great lines that a CMD shows, it displays an installation line that never ends. When I try to cancel the installation, I must restart my PC completely.
Note: the last line is always beginning with "reify:something: timing ... Completed in Xms"
My problem
I've tried to reinstall NodeJS, It did not change a single thing.
I've tried to delete the cache, nothing changed.
I have used npm in the past and it always worked fine, I have absolutely no idea why it doesn't work now.
Please help me, I don't know what to do, except to throw my PC out the window.
I'm on Windows 10, using npm 7.24.1 with node v14.17.6
Finally, I fixed my problem thanks to Marcel Herd: I installed WSL 2 and from now on I'll use Ubuntu on Windows to execute npm commands.
However, I have still no idea why I had to do such a thing...
Thank you
If you are interested, here are links that helped me:
https://learn.microsoft.com/en-us/windows/wsl/install
https://learn.microsoft.com/en-us/windows/wsl/setup/environment
https://learn.microsoft.com/fr-fr/windows/dev-environment/javascript/nodejs-on-wsl
As you saw in the title the command npm does not return anything (as in returning to input again) but is a registered command on Powershell. I have tried removing all nodejs and npm folders and retrying installing it with utilities like nvm, but none of them seem to work. As far as I have checked there is no log output.
Never mind. I found out what was wrong, my CMD was being blocked by a registry key, deleted that and it worked. Thank you!
I have paths to Node and NPM in both my user defined environment variable PATH and in system variable Path.
For node: C:\Program Files\nodejs
For npm: C:\Users\Username\AppData\Roaming\npm
Now node and npm are recognized by Windows Command Prompt but not by WebStorm's terminal. I get error:
'node' is not recognized as an internal or external command
Does anyone know what is problem? I could use WebStorm's terminal normally till today, but something went wrong and now I'm stuck.
EDIT:
echo %PATH% screenshot:
Settings/Tools/Terminal
screenshot:
I had similar issue. I had to select File -> Exit from the IntelliJ application as opposed to using IntelliJ's internal restart option: File -> Invalidate Caches / Restart -> Just Restart.
I had the similar problem like this.I was working with my project with another computer. and after that i decide to work with this project with my computer.so after moving the Files of project. i installed the Node.js and i had all of the paths about Node but when i was want to Run the project. i had this problem. i search a lot but nothing works. so i guess maybe when i restart my computer the new paths of variable system will work well. i restarted and my problem solved!
For those who are encountering this problem when you try to edit the run configuration, you have to put "start" as the command instead of "npm". By default Webstorm knows it's a npm project so it already starts with npm, you simply have to put the start command after that.
I've been trying to get node.js installed on my home PC for a while now with no luck. I've tried different versions for the past couple months and no matter what I try it starts rolling back the install at "Creating shortcuts" and it fails to install. I created an install log for anyone who wants to look at it and take a stab at helping me solve the problem. Thanks!
https://dl.dropbox.com/u/177486/MSIf99e3.LOG
I have faced the same problem, I have resolved my issue. I just mark performance counter to Install when required during installation of node.js
Windows Installer is reporting that it's installed even though it's been rolled back.
Run msiexec /x {29552F29-7FE9-441F-BC56-E6B591587A59}
Where the above guid is the ProductCode value from your log.
If that doesn't work and you have access to Orca.exe from the Windows SDK, you may be able to modify WixSchedInternetShortcuts to a false condition and install successfully. To do that, install Orca, then right click on the node.js msi file and choose 'Edit with Orca' then:
Highlight InstallExecuteSequence under "Tables" on the left.
Find WixSchedInternetShortcuts in the right
Double-click the Condition cell and change VersionNT > 400 to 0
Go to File -> Save
Run the installer again
After installing this version, you should be able to cleanly remove it via Add/remove programs and install another version without modifying the msi file.
I had the same problem with v0.10.35. (23 Jan 2015)
All I had to do was disable the shortcuts in the custom install pane and it worked fine:
My solution
You must install each item separately.
Npm package manager
Add to path
Online documentation ...
Nodejs runtime / Performans counter
(İmportant) nodejs runtime / Event tracing(etw) (select"feature will be installed be required"
restart computer
Last install view
All above methods do not work.
-running msiexec as admin
-msiexec /x ...
-modifying WixSchedInternetShortcuts
-dropping the row WixSchedInternetShortcuts
-even this: removing the option of creating shortcut to online documentation during the installation
Might manually fix it, you can read this help to install product and then add C:\Program Files\nodejs Path to Windows Environment variables.
Open the command promt and paste the below comman
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib_V2Providers{793c9b44-3d6b-4f57-b5d7-4ff80adcf9a2}" /s
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib_V2Providers{1e2e15d7-3760-470e-8699-b9db5248edd5}" /s
If you get a result for the command , go to the registry key and delete that key. Now try to install it again. You should be able to install it now.
msiexec /i node.msi /qn+ ADDLOCAL=ALL REMOVE=NodePerfCtrSupport,NodeEtwSupport
This might help
Had the same problem. Solution 1 provided by Jim Schubert did not fix it. I then used Orca to edit the installation file. Changing the VersionNT condition also did not fix it for me. I then just dropped the rows from WixSchedInternetShortcuts and it installed successfully. I guess it had some problem with writing the shortcuts. I had also previously tried running msiexec as admin ("/a" option), but this didn't fix it...
One point to be aware of (I learn it the hard way): even after having edited the installer with Orca, don't try to uncheck the checkboxes for shortcuts creation in the installer, leave them checked or it will fail with the same error message.
It happened to me as well, I removed almost everything from the installation and completed the installation. After that I ran the installation again and added one by one until I installed all.
You can always use chocolately install:
https://chocolatey.org/packages/nodejs.install/8.11.1
choco install nodejs.install --version 8.11.1
Check if Avast Antivirus is installed in your machine.
If it is turn off the shields and try installing nodejs
Now it works completely fine...
Everytime I double click winghci.exe an error message CreateGHCiProcess failed with failed with error 2 pops. I assume the installation hasn't completed setting environment variables successfully since cmd C:\>ghci ends up with no command found either. Could anyone help posting changes that might take place during the installation or any solution to this?
To complete the incomplete answer: add the path of the bin directory inside your haskell platform folder, e.g. C:\Programs\Haskell Platform\2012.2.0.0\bin, to your PATH. That should be all.
Issue closed. Solution is to set $PATH$ by either reinstallation or manual
I think that's supposed to be %PATH% when you're dealing with windows. path = c:\programs\Haskell Platform\2012.2.0.0\bin;%path% for your example.You could also make a shortcut and point the "Start in:" entry at where you've installed the bin directory.For me, I have it installed under "c:\users[ME]\my documents\dev\Haskell Playform\2013.2.0.0\bin"Starts up fine.