Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm failing to find post script file windows #35

Closed
HyShai opened this issue Apr 17, 2014 · 2 comments
Closed

npm failing to find post script file windows #35

HyShai opened this issue Apr 17, 2014 · 2 comments

Comments

@HyShai
Copy link

HyShai commented Apr 17, 2014

I tried this using the unsafe-perm flag, same error occured

    > [email protected] postinstall C:\Users\redacted\AppData\Roaming\npm\node_modules\prey
    > node ./scripts/post_install.js
The system cannot find the path specified.
{ [Error: spawn ENOENT] code: 'ENOENT', errno: 'ENOENT', syscall: 'spawn' }

> [email protected] preuninstall C:\Users\redacted\AppData\Roaming\npm\node_modules\prey
> node ./scripts/pre_uninstall.js

The system cannot find the path specified.
npm WARN continuing anyway [email protected] preuninstall: `node ./scripts/pre_uninstal
l.js`
npm WARN continuing anyway Exit status 1
npm ERR! [email protected] postinstall: `node ./scripts/post_install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is most likely a problem with the prey package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./scripts/post_install.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls prey
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "c:\\Program Files\\nodejs\\node.exe" "c:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "prey"
npm ERR! cwd C:\Users\redacted
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Users\redacted\npm-debug.log
npm ERR! not ok code 0
@tomas
Copy link
Contributor

tomas commented Sep 22, 2014

Hi,

That's a pretty old version of the client. I'm not sure if you've tried a more recent version, but this should definitely not happen anymore.

@tomas
Copy link
Contributor

tomas commented Sep 23, 2014

I'm closing this one for the time being. Feel free to reopen it the problem still persists in recent versions.

@tomas tomas closed this as completed Sep 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants