Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

it wont work #14345

Closed
fdsfdssdfdf opened this issue Oct 20, 2016 · 1 comment
Closed

it wont work #14345

fdsfdssdfdf opened this issue Oct 20, 2016 · 1 comment

Comments

@fdsfdssdfdf
Copy link

I'm opening this issue because:

Installing dependencies, please wait...
npm ERR! install Couldn't read dependencies
npm ERR! Windows_NT 5.1.2600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs
node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.6.1
npm ERR! npm v2.15.9
npm ERR! path C:\DOCUME1\Owner\LOCALS1\Temp\7zO57B5.tmp\package.json
npm ERR! code ENOPACKAGEJSON
npm ERR! errno -4058
npm ERR! syscall open

npm ERR! package.json ENOENT: no such file or directory, open 'C:\DOCUME1\Owner
\LOCALS
1\Temp\7zO57B5.tmp\package.json'
npm ERR! package.json This is most likely not a problem with npm itself.
npm ERR! package.json npm can't find a package.json file in your current directo
ry.
npm ERR! Windows_NT 5.1.2600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs
node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.6.1
npm ERR! npm v2.15.9
npm ERR! path C:\DOCUME1\Owner\LOCALS1\Temp\7zO57B5.tmp\npm-debug.log.14185889
29
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall rename

npm ERR! EBUSY: resource busy or locked, rename 'C:\DOCUME1\Owner\LOCALS1\Temp
\7zO57B5.tmp\npm-debug.log.1418588929' -> 'C:\DOCUME1\Owner\LOCALS1\Temp\7zO57
B5.tmp\npm-debug.log'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! C:\DOCUME1\Owner\LOCALS1\Temp\7zO57B5.tmp\npm-debug.log
npm WARN retry will retry, error on last attempt: Error: EBUSY: resource busy or
locked, rename 'C:\DOCUME1\Owner\LOCALS1\Temp\npm-12156-fc5fe2e4\registry.npm
js.org\request-\request-2.75.0.tgz.1524425478' -> 'C:\DOCUME1\Owner\LOCALS1\T
emp\npm-12156-fc5fe2e4\registry.npmjs.org\request-\request-2.75.0.tgz'
npm ERR! Windows_NT 5.1.2600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs
node_modules\npm\bin\npm-cli.js" "install" "request"
npm ERR! node v4.6.1
npm ERR! npm v2.15.9

npm ERR! tarball.destroy is not a function
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues
npm ERR! Windows_NT 5.1.2600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs
node_modules\npm\bin\npm-cli.js" "install" "request"
npm ERR! node v4.6.1
npm ERR! npm v2.15.9
npm ERR! path C:\DOCUME1\Owner\LOCALS1\Temp\7zO57B5.tmp\npm-debug.log.34913345
9
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall rename

npm ERR! EBUSY: resource busy or locked, rename 'C:\DOCUME1\Owner\LOCALS1\Temp
\7zO57B5.tmp\npm-debug.log.349133459' -> 'C:\DOCUME1\Owner\LOCALS1\Temp\7zO57B
5.tmp\npm-debug.log'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues
npm WARN retry will retry, error on last attempt: Error: EBUSY: resource busy or
locked, rename 'C:\DOCUME1\Owner\LOCALS1\Temp\npm-12156-fc5fe2e4\registry.npm
js.org\request-\request-2.75.0.tgz.2930640138' -> 'C:\DOCUME1\Owner\LOCALS1\T
emp\npm-12156-fc5fe2e4\registry.npmjs.org\request-\request-2.75.0.tgz'
npm ERR! Windows_NT 5.1.2600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs
node_modules\npm\bin\npm-cli.js" "install" "request"
npm ERR! node v4.6.1
npm ERR! npm v2.15.9

npm ERR! tarball.destroy is not a function
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

@npm-robot
Copy link

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining package.community and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants