You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I noticed this when trying to use the ws module. The fallback files don't get a chance to run because node just seg faults. I assume there is some NAN magic that needs to be upgraded or something? rvagg mentions it in the third paragraph of the first post in nodejs/node#2522 . It would be awesome to get this working for node 4 soon :)
In the meantime, it seems like the fallback files work if I change the source to not even try to require the native versions. So doing that for now.
The text was updated successfully, but these errors were encountered:
Closing this issue, you probably forgot to do a npm rebuild or npm install after switching node versions causing binary addons to be linked against old v8 binaries instead of the new and shiny one's
It's me again...
Same story with this one:
So I noticed this when trying to use the ws module. The fallback files don't get a chance to run because node just seg faults. I assume there is some NAN magic that needs to be upgraded or something? rvagg mentions it in the third paragraph of the first post in nodejs/node#2522 . It would be awesome to get this working for node 4 soon :)
In the meantime, it seems like the fallback files work if I change the source to not even try to require the native versions. So doing that for now.
The text was updated successfully, but these errors were encountered: