-
Notifications
You must be signed in to change notification settings - Fork 17
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
Use meteor-bundled node #2
Comments
I just pushed a new version 0.1.4 to fix this. If you build (Another complication is that if we are providing the libraries in the meteor-spk binary package but taking |
I'm also facing this issue. I'm using meteor-spk 0.1.4, but want to package a meteor v1.2 app which requires node v0.10.40. I tried to build meteor-spk from source, but it keeps linking the wrong version of nodejs (maybe because meteor v1.2 is still in the release candidates stage, and thus not the default?) Any idea how I can fix this (even hacky)? |
OK, I figured out. I replaced the node binary in the deps directory and it works. |
@mquandalle That should work for now. If you're blocked on anything I can help with, let me know! Otherwise meteor-spk updates are likely to happen in a week or two. |
Currently when using meteor-spk, it complains
Meteor requires Node v0.10.36 or later.
If the Meteor bundled node were used, this shouldn't be an issue.
The text was updated successfully, but these errors were encountered: