Skip to content
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

bcrypt 0.7.8 not compatible with the latest Node (0.12.6) #128

Closed
ruchevits opened this issue Jul 6, 2015 · 3 comments
Closed

bcrypt 0.7.8 not compatible with the latest Node (0.12.6) #128

ruchevits opened this issue Jul 6, 2015 · 3 comments

Comments

@ruchevits
Copy link

Changing the following line in .demeteorized/package.json:

"bcrypt": "https://registry.npmjs.org/bcrypt/-/bcrypt-0.7.8.tgz"

to use newer version of bcrypt fixes the issue:

"bcrypt": "0.8.3"

https://www.npmjs.com/package/bcrypt#version-compatibility

@fiveisprime
Copy link
Collaborator

Is Meteor on 0.12 yet?

@ruchevits
Copy link
Author

Works fine for me. node-fibers support for 0.12 was released a few days ago: laverdet/node-fibers#203

@fiveisprime
Copy link
Collaborator

Right right, but demeteorizer honors the node version that Meteor specifies.
Right now, that is 0.10.36, which bcrypt@0.7.8 does work with.

This is a non-issue because the converted application is meant to run on
node@0.10.36 (check the engines property of the generated package.json) along
with dependencies at the version specified by Meteor.

If you are planning to run the converted application, you'll have to stick with
the version of node that's specified in the package.json engines field or
manually change dependencies after converting.

You can use something like nvm or nave to manage local node versions. That
may help ease your pain. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants