-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Packages that currently do not work with Node.js v4.0 [List] #2798
Comments
engine.io fails, throws errors when you try to run your application. |
I ran into issues with https://www.npmjs.com/package/contextify earlier today |
@xzyfer there is brianmcd/contextify#181 waiting to be tested :) |
Directly affected by old nan dependencies:
These packages depend on nan version between 2.0.0 and 2.0.7, which is also not nice:
That's actually 75% of |
Is there a guide or docs written about porting to the new |
For reference, here's a |
And here's a script from @rvagg that helps automate the changes for the new |
Further, some hoped for documentation for the |
[email protected] + [email protected] upgrade fixes all known issues in Sails |
Error on ubuntu 14.04 couldn't figure out if this was supported yet or not. Trying to do this in a dockerfile with an Ember project. dockerfile: FROM ubuntu:14.04 MAINTAINER Mitchell RUN sudo apt-get update RUN sudo apt-get install curl -y ADD package.json package.json RUN mkdir /src/ RUN npm install -g bower RUN npm rebuild node-sass RUN ember serve EXPOSE 4200 Step 21 : RUN npm rebuild node-sass [email protected] install /src/node_modules/ember-cli-sass/node_modules/broccoli-sass-source-maps/node_modules/node-sass [email protected] postinstall /src/node_modules/ember-cli-sass/node_modules/broccoli-sass-source-maps/node_modules/node-sass |
I have answered ^^ in sass/node-sass#1122 (comment) node-sass fully supports node 4.x since 3.2.0, and 3.3.3 is the current version on npm and GitHub. |
See here: http://stackoverflow.com/questions/17967546/common-gypi-not-found-error-in-node-js rm -rf ~/.node_gyp |
node-sass and node-gyp seem incompatible on my end:
|
@thealphanerd ... fyi (for citgm) |
You're trying to install [email protected] which is a couple years old. Node
|
Closing, we are already well into v5. |
I think a lot of people may stay on v4 as it's been chosen for LTS - should this remain open? |
I think the original meaning of this bug is to catch native extensions that didn't upgrade to the (significantly changed) node 4.0 APIs. Not sure how many of them are left to be upgraded (my guess is that probably not so many, but that's just a guess). |
You can still link to it. Perhaps it may be better to link this from one of the Wiki pages. However, there isn't anything actionable here for us anymore so I'd like to trim down our open issues. :) |
I would like to list up the modules not work well on v4.0.
inspired by #456
If this idea is not so good, feel free to close this issue.
The text was updated successfully, but these errors were encountered: