node-red stopped working suddenly

[Hassan Ali Hassan]

Hi everybody,

I have an urgent problem with no clear cause. Node red was working perfectly on my computer. However, tried to run it from cmd and I go " 'node-red' is not recognized as an internal or external command,operable program or batch file.". I thought at first that it was a path problem, so I used "echo %PATH%" to make sure that the node.js directory is included. What could be the cause? Thanks in advance.

[Hassan Ali Hassan]

Sorry Guys, it seems that I panicked for a moment, although it turned out it needed a simple fix. I inspected another device's path (which has node red working properly on it) and I found that I was missing  "C:\Users\user\AppData\Roaming\npm\". when I added that to the environment variables (both system and user), node red started properly. Thank you guys.

[Julian Knight]

A slight failing of Node.JS on Windows is that any global npm installations are not global at all! They are installed to the currently logged in user. Somewhat annoying. You could try using the Windows Ubuntu Subsystem to avoid this issue but that is only in beta right now. Not sure why you didn't have that link though as the Node.JS installation should have set everything correctly and the node-red command should work without any issues as long as you are logged in as the user that installed node-red in the first place.

Also note that the advantage of the way Node.JS works on Windows is that you don't need elevated rights to do npm -g installs.