-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Sails fails to run / install on Node 4.0.0 #3211
Comments
Try |
ah, ok. is there anything besides socket.io that still needs to be compiled? |
Looks similar to: socketio/socket.io#2213 |
a temporary workaround would be to re-direct the dependency
see socketio/socket.io#2213 |
Adding to the list: nodejs/node#2798. |
As i realise, i cant use sailsjs in nodejs v4.0.0 now? |
i'm getting the same start up error about Seg fault. Had to switch back to using node 0.12.7 |
i've the same error, sails lift -silly give me :
|
Updating sails package globally and locally resolved this problem for me. |
Latest socket.io (v1.3.7) installs with node v4.0. |
@jldec Thanks for the info - I just tried on a fresh install of Sails and manually bumped the socket.io version in |
My experiences solving this problem: OSX: 10.9.4 Ubuntu: 14.04 Windows 7: |
@rauchg just published socket.io 1.3.7 see socketio/socket.io#2245 (comment) and socketio/socket.io#2254 If y'all wouldn't mind giving that a test, we can bump the sio dep in sails-hook-sockets and publish a patch to NPM asap. |
In my case updating socket.io to 1.3.7 wasn't enough to Node v4.0. As i said in my previous comment, just when i updated my node version to 4.1 things started to work again. (osx and ubuntu) |
Hmm @DiegoZoracKy when I got home and tried on another project, your comment holds true. For me, on a fresh install of Sails.js with Node 4.0.0 it appeared to work (though there was just one API controller). On a realistic install of Sails.js with more dependencies and setup, I had to switch to Node 4.1.0 as mentioned above. But I can confirm that with Node.js 4.1.0 that this bug is gone for me! Thanks all! |
@camsjams @DiegoZoracKy @jldec @alyrik @ChALkeR @mikepaggi @tjwebb @sgress454 @particlebanana thanks everyone for the help! |
Please note that Node.js 4.1.0 has a security issue at which will make you want to depend on >=4.1.1 once it appears. |
@vielmetti noted - thanks! |
@vielmetti thanks! |
Patched and published Sails v0.11.2. Thanks all! |
Same issue / fresh install node stable (5.0) |
@digitalskyline I was able to install Sails on Node 5 without error. Make sure you clear your npm cache first ( |
also remove your node_modules directory for good measure. |
Per balderdashy#3211, this version of microtime doesn't work with Node 4, and is trivially replaceable with `process.hrtime` from the standard library. Patch mostly applied from commit b0b94c9 in the upstream repository. You probably want to view this diff with whitespace changes disabled, the actual diff is very short.
Per balderdashy#3211, this version of microtime doesn't work with Node 4, and is trivially replaceable with `process.hrtime` from the standard library. Patch mostly applied from commit b0b94c9 in the upstream repository. You probably want to view this diff with whitespace changes disabled, the actual diff is very short.
I was dead in the H2O -- ready to move my beta from prototype/sails to beta/strapi. Here's what I did instead (because I like Sails more)... |
The text was updated successfully, but these errors were encountered: