3 ms·

Node.js 0.8 sounds great, though I'm afraid there will again be a long period where many of your NPM dependencies are simply broken, especially with the new bui

by bergie 14y ago

Node.js 0.8 sounds great, though I'm afraid there will again be a long period where many of your NPM dependencies are simply broken, especially with the new build tool for native modules: https://github.com/TooTallNate/node-gyp https://github.com/TooTallNate/node-gyp We had a bit of a similar situation with the transition from 0.4 to 0.6 because of some API changes, especially the removal of EventEmitters from the C++ module API: https://groups.google.com/d/topic/nodejs/rmvA434u3Dk/discussion https://groups.google.com/d/topic/nodejs/rmvA434u3Dk/discuss... Hopefully this time it will happen more smoothly.

catch23 14y ago
compiling & debugging native libs in node 0.7 is vastly easier, so I'm happy that 0.8 will be here soon. Previously you'd get a pretty generic hardcoded error message about failure to compile/link and it wouldn't be obvious what was the underlying issue. Also, gyp is a lot easier to use than waf -- it just generates the makefiles that are used to do the compilation. The solution was to compile in 0.7 to see the error, then go back to 0.6 to make the module. (I'll also mention I haven't run into any native compatibility issues between 0.6 & 0.7 yet)
ak217 14y ago
We had a really craptastic time trying (and failing) to debug what seems to be race conditions in waf (it uses two workers by default, and they get deadlocked intermittently when doing build jobs). So I look forward to at least getting that sorted out by way of node abandoning waf.