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

Error installing on iojs 3.0.0 #242

Closed
eugene1g opened this issue Aug 20, 2015 · 8 comments · Fixed by #302
Closed

Error installing on iojs 3.0.0 #242

eugene1g opened this issue Aug 20, 2015 · 8 comments · Fixed by #302

Comments

@eugene1g
Copy link

Socket.io fails to build on the recently release iojs 3 (as per socketio/socket.io#2213) which means webpack-dev-server fails to build as well. Leaving the issue here as a reference note, but nothing can be done about this until the upstream problem is resolved.

P.S. socket.io fails because of the ws dependency issue as tracked at websockets/ws#549 which has been fixed with updated dependencies as per websockets/ws@ee66071 and awaits publishing to npm. Once ws publishes, socket.io will bump it's dependency version, then webpack-dev-server should work on iojs 3

@framerate
Copy link

Confirming I see this exact behavior!

@dlong500
Copy link

Is this fixed now that Nodejs 4.0 (based on iojs) is released?

@eugene1g
Copy link
Author

webpack-dev-server relies on socket.io, and socket.io currently cannot be compiled on Nodejs4. However, the patch has been applied to socket.io (socketio/socket.io@210e688) and now webpack awaits for them to cut a new release. A lot of other projects are in the same boat, so it's likely to happen very soon.

@lucasterra
Copy link

@dlong500 no.

@ChALkeR
Copy link

ChALkeR commented Sep 12, 2015

Adding to the list: nodejs/node#2798.

@eugene1g
Copy link
Author

webpack-dev-server depends on two socket.io packages that have just been patched to work on iojs3 or node4. They haven't cut new releases yet, but you can change the webpack-dev-server package.json file to use the patched versions directly like so

    "socket.io": "socketio/socket.io#210e68",
    "socket.io-client": "socketio/socket.io-client#4c22f3",

Of course this hack isn't a lasting solution and can't be done in production, but for now it's a simple workaround to get the dev-server stuff working again in your dev environment.

@SpaceK33z
Copy link
Member

A new version of socket.io including the patch is now released, so after re-adding the webpack-dev-server package this issue should be fixed. Please test this.

@jdhiro
Copy link

jdhiro commented Sep 21, 2015

@SpaceK33z I've confirmed that it works now.

SpaceK33z added a commit to CodeYellowBV/webpack-dev-server that referenced this issue Oct 24, 2015
This removes the node-gyp dependency :).

Fixes webpack#229, webpack#276, fixes webpack#195, fixes webpack#267, fixes webpack#258 and fixes webpack#242
Devhunter416 added a commit to Devhunter416/angular2-rxjs-chat that referenced this issue Dec 22, 2023
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

Successfully merging a pull request may close this issue.

7 participants