-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Issues with grunt build using node 0.11.x? #604
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
Comments
That is strange, seems js-bson wasn't able to compile the bindings on install. Typically thats an issue with node-gyp/python. I do understand your main point though, it does make it harder to track down issues especially when one passes and the other doesn't. A thought though, many people do use the 0.11.x branches of node for several reasons:
I had hoped by adding the beta branch of node to the travis build that we would be able to catch future problems before they landed in stable, but if this is causing more problems then its worth; then I vote to remove it for the time being. |
I would like to test against it for those reasons as well, but maybe we should wait until its a bit closer to a release candidate, which will give other libraries time to fully support it. |
Sounds like a plan. |
I'm not sure if we should be testing against the unstable 0.11.x versions of node. Getting strange failures on the travis builds when trying to
grunt build
projects as part of the tests: https://travis-ci.org/DaftMonk/generator-angular-fullstack/builds/36520974The text was updated successfully, but these errors were encountered: