Don't forget to npm cache clean before you do it. Reinstall the modules with npm install -g. For other OS, see Command to remove all npm modules globally? I believe that since npm installs Node.JS as a package (just like it would React or any other package) to your project, you can just npm install node to get the latest version. On Windows, delete (or rename) the %appdata%\npm directory. You can also do it manually, of course )ĭelete all modules. (I didn't get this to work with findstr in a pipe, hence the roundtrip to the editor. In an editor, format the output for the command line by replacing \n?+ (regex) with a single space.
Npm list -g -parseable -depth=0 > npm-global-modules.txt writes them to a file in your cwd.Īny strange stuff you didn't install yourself has probably been installed by another module (rare, but I have seen it happen). Npm list -g -depth=0 lists all top-level packages, with version numbers. Once the cache is empty, just run npm update -g again.ĭelete the modules you have installed globally, then reinstall them. Npm cache clean usually fixes the problem. Package problems were all fixed with npm update -g. msi package, overwriting the one installed on my system. I have moved from 0.8 to 0.10, using the. For the record, I have just gone through the process, and it is painless even if you upgrade to another major version.
0 kommentar(er)
