npm ERR! EBUSY: resource busy or locked, rmdir 'C:\Users\user\AppData\Roaming\npm\node_modules\deepify\bin\commands' on Windows

[eistrati]

C:\Users\user>npm install deepify -g
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs
node_modules\npm\bin\npm-cli.js" "install" "deepify" "-g"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! path C:\Users\user\AppData\Roaming\npm\node_modules\deepify\bin\com
mands
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall rmdir

npm ERR! EBUSY: resource busy or locked, rmdir 'C:\Users\user\AppData\Roamin
g\npm\node_modules\deepify\bin\commands'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues
npm ERR! error rolling back Error: EBUSY: resource busy or locked, rmdir 'C:\Use
rs\user\AppData\Roaming\npm\node_modules\deepify\bin\commands'
npm ERR! error rolling back at Error (native)
npm ERR! error rolling back { [Error: EBUSY: resource busy or locked, rmdir 'C:
\Users\user\AppData\Roaming\npm\node_modules\deepify\bin\commands']
npm ERR! error rolling back errno: -4082,
npm ERR! error rolling back code: 'EBUSY',
npm ERR! error rolling back syscall: 'rmdir',
npm ERR! error rolling back path: 'C:\Users\user\AppData\Roaming\npm
\node_modules\deepify\bin\commands' }

npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\user\npm-debug.log

[eistrati]

We were able to reproduce this issue again and working now to add more check points in place. Regarding the earlier issue with code EBUSY errno -4082, it looks like this is a known issue and we'll keep monitoring it as well: npm/npm#7370 (somebody suggests reboot or kill all npm processes, others npm cache clean)

[eistrati]

@dbaldon I have checked npm/npm#7370 again and it doesn't look like npm folks were able to solve this issue. Can you please try to use node v6+ on Windows and see if this problem persists?

[dbaldon]

I deleted my comment because I figured out that I had entered the command
incorrectly. I had inadvertently put a dash (-) in front of
ember-cli@1.13.13 which caused the argument to be ignored and npm thought
it was being told to install (upgrade?) itself.

On Sat, Sep 3, 2016 at 9:04 AM eistrati notifications@github.com wrote:

@dbaldon https://github.com/dbaldon I have checked npm/npm#7370
npm/npm#7370 and it doesn't look like npm
folks were able to solve this issue. Can you please try to use node v6+ on
Windows and see if this problem persists?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#273 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK7ehDV0eLXShn9cksqwe3GkvjvxDSwgks5qmX5_gaJpZM4HtLnq
.

[eistrati]

@dbaldon Thanks for getting to the bottom of the problem and sharing your findings. We'll try to learn from your experience and add some extra validations to avoid similar issues in future.

[adirzoari]

@eistrati i have the same problem, have your resolved it?

C:\Users\Adir\MyApps\tasklist>ionic serve
shell.js: internal error
Error: EBUSY: resource busy or locked, open 'C:\Users\Adir\AppData\Local\Temp\shelljs_93017b21a57964622e1d'
at Error (native)
at Object.fs.openSync (fs.js:640:18)
at Object.fs.writeFileSync (fs.js:1333:33)
at execSync (C:\Users\Adir\AppData\Roaming\npm\node_modules\ionic\node_modules\shelljs\src\exec.js:67:57)
at Object._exec (C:\Users\Adir\AppData\Roaming\npm\node_modules\ionic\node_modules\shelljs\src\exec.js:179:12)
at Object.exec (C:\Users\Adir\AppData\Roaming\npm\node_modules\ionic\node_modules\shelljs\src\common.js:168:23)
at Object.gatherGulpInfo (C:\Users\Adir\AppData\Roaming\npm\node_modules\ionic\node_modules\ionic-app-lib\lib\info.js:201:24)
at Object.t (C:\Users\Adir\AppData\Roaming\npm\node_modules\ionic\lib\utils\stats.js:148:15)
at Object.run (C:\Users\Adir\AppData\Roaming\npm\node_modules\ionic\lib\cli.js:135:16)
at Object. (C:\Users\Adir\AppData\Roaming\npm\node_modules\ionic\bin\ionic:13:10)

[eistrati]

@adirzoari It looks like an issue with npm on windows. Check out below link and see if it solves your problem: npm/npm#7370

[haroldjcastillo]

I resolved with npm cache clean or with meteor 'meteor npm cache clean'

[HectorRPL]

@haroldjcastillo haroldjcastillo thanks! works for me

[Ahtesham519]

"npm cache clean" works for me 👍
i also re-installed the meteor .

[abhishek11210646]

worked for me by uninstalling antivirus (bytefence antivirus).

[danielpk74]

It works for me with "npm rebuild", "npm cache clear --force", "npm install"

[godwin-l]

In Windows 10 64-bit OS, I have resolved this issue by uninstalling Anti-Malware software.

[karthick-srinivasan]

In my case, i just restarted my machine and now its working.

[dgpro]

Nothing worked for me until I removed all the packages from package.json and installed them manually npm install -D package1 package2 packageN (-D for devDependencies only). Apparently some of them were outdated and required old dependencies which were breaking things.

[neudesicchetan]

CLose CMD prompts/ Powershell or folder explore on that path . Try again . Will work .

[antonpegov]

CLose CMD prompts/ Powershell or folder explore on that path . Try again . Will work .

Definately not