ChatGPT解决这个技术问题 Extra ChatGPT

How do you uninstall all dependencies listed in package.json (NPM)?

If I have a package.json file defined in my application root and run npm install -g it will install all the dependencies defined in package.json, globablly.

However, this doesn't seem to work in reverse.

If I do npm uninstall -g in my application root it throws an error, expceting me to pass it a package name.

Shouldn't this also uninstall the same packages I installed?

Am I doing something wrong?

FYI my reasoning behind never using npm -g. peterlyons.com/problog/2012/09/…
Remember that if you want to use a module for your project, you have to install it locally. Installing a module globally only provides more commands in your terminal, as with expressjs and express(1) for instance.
@sgwilly You're wrong about having to use node_modules globally -- it even says so in the docuemention - nodejs.org/api/modules.html#modules_all_together - the require() function is 'smart' in that it looks in various location to try and resolve a path for a module including the global node_modules
I should have been more specific : it's true that require() is smart enough to find your globally installed module. It'll work if all your projects depend on the same version of that said module. Yet, you might have a hard time maintaining projects relying on different module versions if you only manage dependencies globally. That's why it's best practice to always install modules locally, and only install them globally when you want to get access to some handy executable commands.
@sgwilly - thanks for sharing your thoughts here -- this project in particular is a distributable so it should not be trying to update anything -- the actually updates will happen over RPM (note RPM not NPM) and the actual node_modules are shrinkwrapped -- I just needed a way to quickly clean the system of whatever the rpm ended up installing (in my dev environment)

j
jedmao

If using Bash, just switch into the folder that has your package.json file and run the following:

for package in `ls node_modules`; do npm uninstall $package; done;

In the case of globally-installed packages, switch into your %appdata%/npm folder (if on Windows) and run the same command.

EDIT: This command breaks with npm 3.3.6 (Node 5.0). I'm now using the following Bash command, which I've mapped to npm_uninstall_all in my .bashrc file:

npm uninstall `ls -1 node_modules | tr '/\n' ' '`

Added bonus? it's way faster!

https://github.com/npm/npm/issues/10187


You posted the exact same command as an answer to "Command to remove all npm modules globally?". How can this be the appropriate thing to do in both that situation and this one?
@AndrewMedico How is it not appropriate? Packages installed in your package.json file will be installed in your node_modules folder. This command will take every sub-folder to the node_modules folder and run npm uninstall <package> for each folder. I did this myself and it works excellently!
@UgoRobain good question. As it turns out, some dependencies get really deep. On the NTFS file system (Windows), at least, it has problems removing directories where the path name is longer than some kind of limit, leaving these phantom directories that you can't remove. Fortunately, npm uninstall takes care of that, which is why this trick is useful.
Here's what I used to do it with powershell: foreach($package in ls node_modules){npm uninstall $package}
doesn't seem to work on windows. tr is not recognized
D
Druubacca

This worked for me:

command prompt or gitbash into the node_modules folder in your project then execute:

npm uninstall *

Removed all of the local packages for that project.


Doesn't this remove global installs too?
@shinzou It did not remove global installs for me.
On Mac 10.13.5, this throws lots of error as below "> heapdump@0.3.9 install /Users/vikramanna/node_modules/heapdump > node-gyp rebuild CXX(target) Release/obj.target/addon/src/heapdump.o In file included from ../src/heapdump.cc:17: ../src/compat-inl.h:300:19: error: no member named 'GetCpuProfiler' in 'v8::Isolate' return isolate->GetCpuProfiler()->StartProfiling(title, record_samples);"
S
Sameer

For windows go to node_modules dir and run this in powershell

npm uninstall (Get-ChildItem).Name 

For me, this results in the error "The command line is too long."
b
brismuth

I recently found a node command that allows uninstalling all the development dependencies as follows:

npm prune --production

As I mentioned, this command only uninstalls the development dependency packages. At least it helped me not to have to do it manually.


y
y0n1

Tip for Windows users: Run this PowerShell command from within node_modules parent directory:

ls .\node_modules | % {npm uninstall $_}

T
Terry Young
// forcibly remove and reinstall all package dependencies
ren package.json package.json-bak
echo {} > package.json
npm prune
del package.json
ren package.json-bak package.json
npm i

This essentially creates a fake, empty package.json, calls npm prune to remove everything in node_modules, restores the original package.json and re-installs everything.

Some of the other solutions might be more elegant, but I suspect this is faster and exhaustive. On other threads I've seen people suggest just deleting the node_modules directory, but at least for windows, this causes npm to choke afterward because the bin directory goes missing. Maybe on linux it gets restored properly, but not windows.


In my case - I did not need the existing package.json (because of running the script on CI after npm scripts were executed..) So I just went with: "echo {} > package.json & npm prune"
G
Gntem

Actually there is no option to do that, if you want to uninstall packages from package.json simply do npm ls on the same directory that package.json relies and use npm uninstall <name> or npm rm <name> for the package you want to remove.


I know how to remove them individually -- it would just make more sense if there was a command to run against the package.json file the same way npm install works.
No we don't want to uninstall by hand every module.
H
Harsh Phoujdar

Another SIMPLE option is to delete the node_modules and package-lock.json

rm -rf node_modules
rm -rf package-lock.json

After this you can try reinstalling the npm packages


Thanks for this suggestion. I had no global packages. Most responses are talking about -g option! I had horrible time getting rid of ALL local packages because not knowing enough about nodejs/npm, I did 'npm install this-and-that' from several different directories. When I use 'npm uninstall ', the 'npm ls' still shows some packages. I am shell programmer so tried 'npm uninstall' on every imaginable part of the 'npm ls' output. None worked to get rid of ALL packages. Tired, but found this suggestion and fixed my issue in 5 minutes. Thanks Harsh.
I don't know what the purpose of package.json, package-lock.json, node_modules, dependencies, local/global differences, or how nodejs/npm works. I use a nodejs module that is needed for another program. Since I installed many different modules with 'npm install' from different directories, I wanted to get rid of ALL of them at once. None of the other answers are talking about this. Using this and 'find' command on linux, I was able to get rid of everything in 5 minutes. Don't know why nobody else found this helpful yet.
I am glad to be of help @BReddy, I always prefer/try to figure the simple yet effective approach
a
amrography

First, remove all packages from dependencies and devDependencies in package.json

Second, run npm install

That simple.


Didn't delete all the folders, but removed most of the files allowing File Explorer to be able to delete the rest.
L
Lakmi

remove unwanted dependencies from package.json npm i

"npm i" will not only install missing deps, it updates node_modules to match the package.json


V
Valentine Bondar

Powershell users: foreach($package in ls node_modules){npm uninstall $package}

Thanks @JustMailer


s
siOnzee

(Don't replicate these steps till you read everything)

For me all mentioned solutions didn't work. Soo I went to /usr/lib and run there

for package in `ls node_modules`; do sudo npm uninstall $package; done;

But it also removed the npm package and only half of the packages (till it reached letter n).

So I tried to install node again by the node guide.

# Using Ubuntu
curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -
sudo apt-get install -y nodejs

But it didn't install npm again.

So I decided to reinstall whole node sudo apt-get remove nodejs And again install by the guide above.

Now is NPM again working but the global modules are still there. So I checked the content of the directory /usr/lib/node_modules and seems the only important here is npm. So I edited the command above to uninstall everything except npm

for package in $(ls node_modules); do if [ "$package" != "npm" ]; then sudo npm uninstall $package; fi; done;

It removed all modules what were not prefixed @. Soo I extended the loop for subdirectories.

for package in $(ls node_modules); do if [  ${package:0:1} = \@ ]; then 
        for innerPackage in $(ls node_modules/${package}); do
                sudo npm uninstall "$package/$innerPackage";
        done;
fi; done;

My /usr/lib/node_modules now contains only npm and linked packages.


V
VIKAS KOHLI

Even you don't need to run the loop for that.

You can delete all the node_modules by using the only single command:-

npm uninstall `ls -1 node_modules | tr '/\n' ' '`

R
Ryan Lecha

Piggy-backing off of VIKAS KOHLI and jedmao, you can do this

single line version:

npm uninstall `ls -1 node_modules | grep -v ^@ | tr '/\n' ' '` `find node_modules/@* -type d -depth 1 2>/dev/null | cut -d/ -f2-3 | tr '\n' ' '`

multi-lined version:

npm uninstall \
`ls -1 node_modules | grep -v ^@ | tr '/\n' ' '` \
`find node_modules/@* -type d -depth 1 2>/dev/null | cut -d/ -f2-3 | tr '\n' ' '`

d
dakota zinn

Since this is still the first result on the Googler when searching how to remove all modules in NPM, I figured I'd share a small script for Powershell to remove all dependencies through NPM:

#Create a Packages Array to add package names to
$Packages = New-Object System.Collections.ArrayList

#Get all Production Dependencies by name
(Get-Content .\Package.json | ConvertFrom-JSON).dependencies.psobject.properties.name |
ForEach-Object { $Packages.Add($_) | Out-Null }

#Get all Dev Dependencies by name
(Get-Content .\Package.json | ConvertFrom-JSON).devDependencies.psobject.properties.name | 
ForEach-Object { $Packages.Add($_) | Out-Null }

#Remove each package individually
Foreach($Package in ($Packages | select -unique))
{ npm uninstall $Package }

#Clean up any remaining packages
$Modules = Get-ChildItem "node_modules"
if($Modules)
{ $Modules | ForEach-Object { Remove-Item ".\node_modules\$_" -Force -Recurse } }

This runs a more specific removal, rather than removing each module from node_modules individually.