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

node-gyp fails with node v4 on windows #2750

Closed
luisrudge opened this issue Sep 9, 2015 · 7 comments
Closed

node-gyp fails with node v4 on windows #2750

luisrudge opened this issue Sep 9, 2015 · 7 comments
Labels
question Issues that look for answers. windows Issues and PRs related to the Windows platform.

Comments

@luisrudge
Copy link

with node:latest on windows, running npm i c3 fails every time.

websockets/bufferutil#15
websockets/utf-8-validate#13
brianmcd/contextify#177

@luisrudge luisrudge changed the title node-gyp fails everytime with node v4 on windows node-gyp fails with node v4 on windows Sep 9, 2015
@cjihrig
Copy link
Contributor

cjihrig commented Sep 9, 2015

I haven't tested on Windows, but npm i bufferutil worked for me, while npm i [email protected] (which is the version reported in the issue) does not. It seems to use an older version of nan. Looks to be a similar situation for the other issues.

@ronkorving
Copy link
Contributor

Latest bufferutil uses the latest NAN and breaks on Node 4.

@mscdex
Copy link
Contributor

mscdex commented Sep 9, 2015

@luisrudge @ronkorving The issue with bufferutil in particular is that the upstream project(s) have not updated their dependencies so that bufferutil 1.2.x is picked up, which is what has nan 2.x support (not bufferutil 1.1.0).

So currently that means that engine.io-client needs to bump ws to v0.8.0, then afterwards socket.io-client needs to bump engine.io-client, then socket.io needs to bump socket.io-client.

@ronkorving
Copy link
Contributor

I'm already on ws v0.8. Still broken, and it wasn't on iojs v3

@brendanashworth brendanashworth added the windows Issues and PRs related to the Windows platform. label Sep 9, 2015
@mscdex
Copy link
Contributor

mscdex commented Sep 9, 2015

@ronkorving npm install ws works just fine for me with node v4 on Windows. However what I meant earlier was that for socket.io specifically, its dependency chain has to be updated yet to use ws v0.8.

@ronkorving
Copy link
Contributor

Sure, but that's not the problem here (I'm not even using socket.io, I use ws directly). This is a real problem, but I haven't been able to determine where its origin is. See websockets/bufferutil#15 (comment)

@bnoordhuis
Copy link
Member

I'm going to close this because it's almost certainly not an issue with node core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Issues that look for answers. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

No branches or pull requests

7 participants