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 update #75

Closed
polikin opened this issue Feb 20, 2014 · 19 comments
Closed

npm update #75

polikin opened this issue Feb 20, 2014 · 19 comments

Comments

@polikin
Copy link

polikin commented Feb 20, 2014

I updated the package and now, it's not working anymore. Try to re-install, same error.

ws@0.4.31 install C:\Users\****\AppData\Roaming\npm\node_modules\browser-sync\node_modules\socket.io\node_modules\socket.io-client\node_modules\ws (node-gyp rebuild 2> builderror.log) || (exit 0)

'browser-sync' is not recognized as an internal or external command, operable program or batch file.

@shakyShane
Copy link
Contributor

Seems like the install failed - possibly due to an npm problem. Try again with -g

@polikin
Copy link
Author

polikin commented Feb 20, 2014

I did it with -g.

http://screencast-o-matic.com/u/VAds/browser-sync

@shakyShane
Copy link
Contributor

This may help until I look into this myself

socketio/socket.io#1126

@polikin
Copy link
Author

polikin commented Feb 20, 2014

The problem is here: npm install socket.io. Don't know why it doesn't work now. I did an update few weeks ago and everything was fine.

@HugoHeneault
Copy link

I have a similar issue a few weeks ago, it started because browser-sync was working while updating.
I had to delete the whole node_modules folder and run npm install again.

@shakyShane
Copy link
Contributor

Yeah I'm looking into this - no idea why this is happening :(

@shakyShane shakyShane added the bug label Feb 21, 2014
@joeyhoer
Copy link

Same issue here. I had a prior version installed and it was working fine. After running a npm update -g and going through what essentially amounted to a reinstall of npm (because of discrepancies in Homebrew and NPM) browser-sync will no longer work.

I reverted back to the last version using:

npm uninstall -g browser-sync
npm install -g browser-sync@0.6.2

@shakyShane
Copy link
Contributor

I still haven't managed to reproduce this yet as my Windows machine is running 8.1 - with no install problems.

If anyone would like to help us out here it'd be much appreciated.

@polikin
Copy link
Author

polikin commented Mar 14, 2014

The problem seems to be socket,io.

ws@0.4.31 install C:\Users\xxxx\AppData\Roaming\npm\node_modules\browser-sync\node_modules\socket.io\node_modules\socket.io-client\node_modules\ws
(node-gyp rebuild 2> builderror.log) || (exit 0)

gyp ERR! configure error
gyp ERR! stack Error: Python executable "python" is v3.3.4, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack at failPythonVersion (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:106:14)

@shakyShane
Copy link
Contributor

Thanks - I may look at using a previous version of socket.io then - or another lib...

@shakyShane
Copy link
Contributor

Can everyone in this thread confirm the following fails & which version of window you're running.

npm install socket.io

@polikin
Copy link
Author

polikin commented Mar 18, 2014

Windows 8, 64bits

gyp ERR! configure error 
gyp ERR! stack Error: Python executable "python" is v3.3.4, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack     at failPythonVersion (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:106:14)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:95:9
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:635:7)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at maybeClose (child_process.js:743:16)
gyp ERR! stack     at Socket.<anonymous> (child_process.js:956:11)
gyp ERR! stack     at Socket.EventEmitter.emit (events.js:95:17)
gyp ERR! stack     at Pipe.close (net.js:465:12)
gyp ERR! System Windows_NT 6.2.9200
gyp ERR! command "node" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\xxxx\AppData\Roaming\npm\node_modules\socket.io\node_modules\socket.io-client\node_modules\ws
gyp ERR! node -v v0.10.26
gyp ERR! node-gyp -v v0.12.2
gyp ERR! not ok 

@joeyhoer
Copy link

I can confirm that I get the same error, and I believe it to be an issue with ws, a dependency of socket.io, not socket.io per se.

> ws@0.4.31 install /usr/local/lib/node_modules/browser-sync/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

I am on OSX 10.9.2/

@jmwohl
Copy link

jmwohl commented Mar 24, 2014

Confirmed, same issue here. Also on OSX 10.9.2.

> ws@0.4.31 install /usr/local/lib/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

@shakyShane
Copy link
Contributor

Ok thanks everyone.

The next release will revert back to a pre 0.9.0 version of socket.io to solve this problem.

@polikin
Copy link
Author

polikin commented Mar 26, 2014

Works! Thanks!

@shinnn
Copy link
Contributor

shinnn commented Mar 27, 2015

I've updated to the latest npm and node.

Not yet.

npm ERR! node v0.12.1
npm ERR! npm  v2.5.1

v2.5.1 is still older version. https://github.com/npm/npm/releases

@olafgleba
Copy link

Issue still exist:

> ws@0.5.0 install /xxx/node_modules/browser-sync/node_modules/socket.io/node_modules/engine.io/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

With using:

node v0.12.1
npm v2.7.3

OS X 10.10.1

@corysimmons
Copy link

bump

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

No branches or pull requests

8 participants