Please update all dependencies

[lepture]

It can't work well on node 4.0

[andresmrm]

Getting segmentation fault (core dumped) webpack-dev-server with nodejs 4.0.
Downgraded to nodejs 0.12.7 and it's working again.

[sokra]

have you tried npm rebuild?

[sample-usr]

I'm getting the same error after updating to node 4.0. Also tried npm rebuild but still the same.

[sample-usr]

Deleted the ~/.node-gyp folder and then did a npm rebuild again which has seemed to work for now. Although I still errors upon installing webpack-dev-server. Same as #258

[lepture]

@razagill coz socket.io depends on an old ws.

[CrocoDillon]

Seems like socket.io is still not updated for Node 4 though, which is sad. Anyway tagging along to get notified when this is fixed.

[ghost]

same problem with node 4.0 caused by socket.io

[ChALkeR]

Adding to the list: nodejs/node#2798.

[eugene1g]

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.

[mattgi]

Need a socket.io fork that also points its dependency of socket.io-client to what you have provided @eugene1g.

So it needs to be:

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

f5b753 being a later commit.

[SpaceK33z]

A new version of socket.io is just released which includes the fix to work on nodejs v4 (1.3.7). I will write a PR for this.

Edit: nvm, package.json uses the ^ so it doesn't need updating :).

Can you verify that this issue is now fixed?

[chemzqm]

Build errors still exist, but only raise on optional deps [https://github.com/BrowserSync/browser-sync/issues/820]. Looks like no impact on daily usage, just ignore them would be fine.