I just updated npm
to 5.4.0
.
Now, Whenever I want install a npm package I get the following error:
D:\Sources\DownloadCms\Md.Download\Web.Angular>npm install mds.angular.datetimepicker@latest --save
npm ERR! path D:\Sources\DownloadCms\Md.Download\Web.Angular\node_modules\fsevents\node_modules\abbrev\package.json
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall unlink
npm ERR! Error: EPERM: operation not permitted, unlink 'D:\Sources\DownloadCms\Md.Download\Web.Angular\node_modules\fsevents\node_modules\abbrev\package.json'
npm ERR! at Error (native)
npm ERR! { Error: EPERM: operation not permitted, unlink 'D:\Sources\DownloadCms\Md.Download\Web.Angular\node_modules\fsevents\node_modules\abbrev\package.jso
n'
npm ERR! at Error (native)
npm ERR! stack: 'Error: EPERM: operation not permitted, unlink \'D:\\Sources\\DownloadCms\\Md.Download\\Web.Angular\\node_modules\\fsevents\\node_modules\\ab
brev\\package.json\'\n at Error (native)',
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'unlink',
npm ERR! path: 'D:\\Sources\\DownloadCms\\Md.Download\\Web.Angular\\node_modules\\fsevents\\node_modules\\abbrev\\package.json' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Mohammad\AppData\Roaming\npm-cache\_logs\2017-09-03T03_25_50_432Z-debug.log
I'm dead sure, run CMD
as administrator.
Also I checked D:\Sources\DownloadCms\Md.Download\Web.Angular\node_modules\fsevents\node_modules\abbrev\package.json\
, package.json
is not exist in path !
Edit: Upgrade to v5.4.1, still get the same error, even cannot work around with --no-optional :-(
It is an npm 5.4.0 issue https://github.com/npm/npm/issues/18287
Workarounds are
- downgrade to 5.3
- try running with --no-optional, i.e.
npm install --no-optional
I was able to fix this by running the command prompt/bash as admin and closing VSCode! Seems like VSCode was locking some files. Potentially something else could be locking these files for you.
If you downgrade to 5.3 and still get the same error in Windows like me.
After hours working with npm versions I found the following solution:
1. Download latest recommended version of nodejs
, these days is node-v6.11.3-x64
2. Uninstall nodejs
with it.
3. Go to C:\Users\{YourUsername}\AppData\Roaming
folder and delete npm
and npm-cache
folders
4. Run installer of nodejs
again and install it
5 Update npm to 5.3 with npm i -g npm@5.3
command line
Now you should use npm without any issues.
I fixed by downgrading npm from 5.4.0 to version 5.3
npm i -g npm@5.3
I Hope this helps for you
I had the same issue and all I needed to do was login to npm
npm login
or alternatively
npm add user
// consult the documentation for the params
I tried this solution found at a How to fix Node.js blog
just use
npm cache clean
in windows if it refuses use
npm cache clean --force
I had the same problem on Windows.
The source of the problem is simple, it is access permission on folders and files.
In your project folder, you need
- After cloning the project, change the properties of the folder and change the permissions of the user (give full access to the current user).
- Remove the read-only option from the project folder. (Steps 1 and 2 take a long time because they are replicated to the entire tree below).
- Inside the project folder, reinstall the node (npm install reinstall -g)
- Disable Antivirus. (optional)
- Disable Firewall. (optional)
- Restart PC.
- Clear the npm cache (npm clear)
- Install the dependencies of your project (npm install)
After that, error "Error: EPERM: operation not permitted, unlink" will no longer be displayed.
Remember to reactivate the firewall and antivirus if necessary.
For me it worked in bash from git package try:
C:\Program Files\Git\bin\bash.exe
then:
npm install mds.angular.datetimepicker@latest
There seems to be many solutions out there that worked with downgrading npm versions. For me, the solution was
npm install -force
I tried the downgrading of npm versions, modifying my npm prefix config to match the npm directory, and clearing cache. None of these worked, but apparently they worked for others, so it may be worth a shot.
npm install npm@5.3 -g
Fixed in NPM 5.6.0
Upgrade to NPM 5.6.0 solved problem for me.
I wanted to run npm install from within my external hard drive as this is where i saved my code workspace. Windows 10 OS.
But I was getting the same error as the original post.None of the previous answers worked for me, I tried all of them:
- uninstalling nodejs then re-installing
- uninstalling nodejs then downgrading/installing a lower version of nodejs.
- npm install -force
- deleting the folders from C:\Users{YourUsername}\AppData\Roaming ... npm and npm-cache then re-installing.
- npm cache clean --force
- npm cache clean
- npm install --g or npm install --global
What worked for me was this:
- copy the folder from C:\Program Files\nodejs to D:\Program Files\nodejs
- Then go to Control Panel\System and Security\System
- Advanced System Settings
- Environment Variables
- System Variables
- Double click Path
- Add a new path
- D:\Program Files\nodejs
- Click ok
- restart PC.
- try npm install from within D: Drive
For me on Windows the problem was too long path length. I moved the project to a smaller length path and it worked.
Please close all IDE like visual studio code. run npm install command through node.js command prompt. Enjoy !
For windows,
- Download latest recommended version of
nodejs
, these days isnode-v6.11.3-x64
- Uninstall nodejs with it.
- Go to
C:\Users\{YourUsername}\AppData\Roaming
folder and deletenpm
andnpm-cache
folders - Run installer of
nodejs
again and install it - By default
npm 3.10.10
should be installed along withnode-v6.11.3-x64
. - It worked for me with
npm 3.10.10
but did not work with5.3.X
. Also it did not worked with higher versions of node (abovenode-v6.11.3-x64
)
I had this logs in Windows. I did the following
- Close Visual Studio Code
- Run Command Line as admin
npm cache verify
solved my issue.
I was doing: ng new my-app
and I faced similar error
I have
node version: 10.16.0
npm v 6.9.0
If all of the above failed to work for you, you might want to
- restart your system
- run command prompt as admin
- run the npm command
My problem was executing the command (npm audit fix all). I solved it when closing VSCODE and re-executed the command without problems.
来源:https://stackoverflow.com/questions/46020018/error-eperm-operation-not-permitted-unlink-d-sources-node-modules-fseven