Some time ago I had trouble with the npm cache on our build machines. From time to time we had to do npm cache clean
by hand, and that solved various issues that we
As npm-config documented:
force§ Default: false Type: Boolean Makes various commands more forceful.
- lifecycle script failure does not block progress.
- publishing clobbers previously published versions.
- skips cache when requesting from the registry.
- prevents checks against clobbering non-npm files.
Maybe use -f
/ --force
is the simplest way to disable npm cache.
npm install --force