Error: EPERM: operation not permitted, unlink

bxqgit commented 7 years ago

Expected behavior

No errors while executing npm install in ./assets directory.

Actual behavior

All commands are run as root/Administrator. I run mix phx.new hello, which suggests to run cd hello and cd assets && npm install && node node_modules/brunch/bin/brunch build afterwards.

When I run npm install in ./assets directory, I get the following error:

npm ERR! path c:\prj\hello\assets\node_modules\nan\package.json
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall unlink
npm ERR! Error: EPERM: operation not permitted, unlink 'c:\prj\hello\assets\node_modules\nan\package.json'
npm ERR!  { Error: EPERM: operation not permitted, unlink 'c:\prj\hello\assets\node_modules\nan\package.json'
npm ERR!   stack: 'Error: EPERM: operation not permitted, unlink \'c:\\prj\\hello\\assets\\node_modules\\nan\\package.json\'',
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'unlink',
npm ERR!   path: 'c:\\prj\\hello\\assets\\node_modules\\nan\\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\foo\AppData\Roaming\npm-cache\_logs\2017-08-28T21_19_41_885Z-debug.log

Is it ok? Does it break my app somehow?

Environment

Elixir version (elixir -v):

Erlang/OTP 20 [erts-9.0] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10]
Elixir 1.5.1

Phoenix version (mix deps):
file_system 0.2.0 (Hex package) (mix) locked at 0.2.0 (file_system) 1b899a87 ok
connection 1.0.4 (Hex package) (mix) locked at 1.0.4 (connection) a1cae722 ok
gettext 0.13.1 (Hex package) (mix) locked at 0.13.1 (gettext) 5e0daf4e ok
ranch 1.3.2 (Hex package) (rebar3) locked at 1.3.2 (ranch) e4965a14 ok
poolboy 1.5.1 (Hex package) (rebar3) locked at 1.5.1 (poolboy) 6b461639 ok
decimal 1.4.0 (Hex package) (mix) locked at 1.4.0 (decimal) fac965ce ok
poison 3.1.0 (Hex package) (mix) locked at 3.1.0 (poison) d9eb6366 ok
db_connection 1.1.2 (Hex package) (mix) locked at 1.1.2 (db_connection) 2865c2a4 ok
phoenix_pubsub 1.0.2 (Hex package) (mix) locked at 1.0.2 (phoenix_pubsub) bfa7fd52 ok
cowlib 1.0.2 (Hex package) (rebar3) locked at 1.0.2 (cowlib) 9d769a1d ok
cowboy 1.1.2 (Hex package) (rebar3) locked at 1.1.2 (cowboy) 61ac29ea ok
mime 1.1.0 (Hex package) (mix) locked at 1.1.0 (mime) 01c1d6f4 ok
plug 1.4.3 (Hex package) (mix) locked at 1.4.3 (plug) 236d77ce ok
phoenix_html 2.10.4 (Hex package) (mix) locked at 2.10.4 (phoenix_html) d4f99c32 ok
phoenix 1.3.0 (Hex package) (mix) locked at 1.3.0 (phoenix) 1c01124c ok
phoenix_live_reload 1.1.1 (Hex package) (mix) locked at 1.1.1 (phoenix_live_reload) 8c9f0fb9 ok
postgrex 0.13.3 (Hex package) (mix) locked at 0.13.3 (postgrex) c277cfb2 ok
ecto 2.2.1 (Hex package) (mix) locked at 2.2.1 (ecto) ccc6fd30 ok
phoenix_ecto 3.2.3 (Hex package) (mix) locked at 3.2.3 (phoenix_ecto) 450c7498 ok
NodeJS version (node -v):
```
v8.4.0
```
NPM version (npm -v):
```
5.4.0
```
Operating system:
```
Microsoft Windows [Version 10.0.15063]
```

raboija commented 5 years ago

This worked for me: ctrl + Alt + Delete, Task Manager, Find all running instances of node server and kill them. install your packages.

basic idea is that your node server keeps running in the background even after you think you've closed it in the console and it is accessing all your node files.

THANK YOU

lynxlangya commented 5 years ago

@LoganSimonsen Oh Thanks Very much, This is very helpful to me.

mkrishna4u commented 5 years ago

its look like windows issue and wait for 1 to 2 minutes and try again then window will release the lock on the file/folder. To me it happens time to time.

DutchKevv commented 5 years ago

Visual studio code's (VS code) integrated terminal created problems for me. For some reason the editor hijacks the files, locking them and so this permission error shows.

If I do it through a standalone terminal, it just works.

Could be windows only problem though, I never had problems with it on linux, also using vscode.

heads up to @jarvar

capt-morgan commented 5 years ago

Visual studio code's (VS code) integrated terminal created problems for me. For some reason the editor hijacks the files, locking them and so this permission error shows.

If I do it through a standalone terminal, it just works.

Could be windows only problem though, I never had problems with it on linux, also using vscode.

heads up to @jarvar

I have a similar experience. Been getting the same error message when bootstrapping lerna from GitBash integrated in WebStorm. Then tried standalone Windows Command and it worked like a charm.

rashmimilan commented 5 years ago

This worked for me: ctrl + Alt + Delete, Task Manager, Find all running instances of node server and kill them. install your packages. basic idea is that your node server keeps running in the background even after you think you've closed it in the console and it is accessing all your node files.

Thanks a ton @LoganSimonsen . The idea worked for me.

Thank you! I followed above steps to resolve the issue.

kuromukira commented 5 years ago

Can't seem to solve this tho. I have restarted my PC several times and still no luck. I also changed the folder permissions.

zzhangpurdue commented 5 years ago

most likely a running node.js application is using it. Make sure to close all of the node.js application.[solved]

dositejg commented 4 years ago

In my case something got messed up with node_modules and package-lock.json, removing them worked for me. To remove node_modules through command line, navigate to your project folder and write rm -R node_modules

jerry-santana commented 4 years ago

I have tried EVERYTHING in this page and nothing has worked for me! When I run the command yarn upgrade @[packagename] it fails immediately with EPERM: operation not permitted. What should I do?

rishav394 commented 4 years ago

Simply closing vscode fixed this for me. Something else might have a lock on some of the node packages. It is the cause of this issue. Example, you might be running the react development server and it creates a lock on the create-react-app files. This can cause the issue.

sabdelkhaliq commented 4 years ago

This worked for me: ctrl + Alt + Delete, Task Manager, Find all running instances of node server and kill them. install your packages.

basic idea is that your node server keeps running in the background even after you think you've closed it in the console and it is accessing all your node files.

Thank you! it works

DavidDolyak commented 4 years ago

Just turn off the app, install a module and run the app again. Worked for me!

shilu-stha commented 3 years ago

@chrismccord I just dropped the npm cache and everything works fine now. It's definitely the issue of npm, not Phoenix.
rd /s /q C:\Users\foo\AppData\Roaming\npm-cache
rd /s /q C:\Users\foo\AppData\Roaming\npm

Worked for me.

RxNationGaming commented 3 years ago

Plz help I got the npm err! Code EPERM on my android device I am using termux like a cmd promt

Mansouri147 commented 3 years ago

That error generally means that a file is being accessed by two different things at 'around' the same time. And 90% of those times it is because of an anti-virus or similar.

Yeah I was facing the same error and this works fine! for my case it was because I'm actually running the app (metro) and trying to update packages by running yarn

alex-shepel commented 2 years ago

That error generally means that a file is being accessed by two different things at 'around' the same time. And 90% of those times it is because of an anti-virus or similar.

It helped me when I terminated localhost. It was started with npm start.

11AA8R4 commented 2 years ago

That error generally means that a file is being accessed by two different things at 'around' the same time. And 90% of those times it is because of an anti-virus or similar.

My google drive auto-backup is accessing it then, you solved the problem for me, i gotta disable it while editing

mamonaabdullah122 commented 2 years ago

Help me i have this issue when i start the serve in angular with command of ng serve or ng serve --open then this error will be appear:Can someone help An unhandled exception occurred: Cannot find module 'electron-to-chromium/versions' Require stack:

/Users/student/Documents/atm-user-interface/node_modules/browserslist/index.js
/Users/student/Documents/atm-user-interface/node_modules/@angular-devkit/build-angular/src/utils/supported-browsers.js
/Users/student/Documents/atm-user-interface/node_modules/@angular-devkit/build-angular/src/utils/normalize-builder-schema.js
/Users/student/Documents/atm-user-interface/node_modules/@angular-devkit/build-angular/src/utils/index.js
/Users/student/Documents/atm-user-interface/node_modules/@angular-devkit/build-angular/src/builders/dev-server/index.js
/Users/student/Documents/atm-user-interface/node_modules/@angular-devkit/architect/node/node-modules-architect-host.js
/Users/student/Documents/atm-user-interface/node_modules/@angular-devkit/architect/node/index.js
/Users/student/Documents/atm-user-interface/node_modules/@angular/cli/models/architect-command.js
/Users/student/Documents/atm-user-interface/node_modules/@angular/cli/commands/serve-impl.js
/Users/student/Documents/atm-user-interface/node_modules/@angular-devkit/schematics/tools/export-ref.js
/Users/student/Documents/atm-user-interface/node_modules/@angular-devkit/schematics/tools/index.js
/Users/student/Documents/atm-user-interface/node_modules/@angular/cli/utilities/json-schema.js
/Users/student/Documents/atm-user-interface/node_modules/@angular/cli/models/command-runner.js
/Users/student/Documents/atm-user-interface/node_modules/@angular/cli/lib/cli/index.js
/usr/local/lib/node_modules/@angular/cli/lib/init.js See "/private/var/folders/vt/w33_jkgx68bdkmfdy9gglvs80000gn/T/ng-wqc8v0/angular-errors.log" for further details.

nestorbfgo commented 2 years ago

One thing that help to resolve this problem was use npm install like admin, I was using yarn before so I dont now why happened it, but using npm install didnt cause me any problem

phoenixframework / phoenix