You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. :)
Changing the following line in
.demeteorized/package.json
:to use newer version of
bcrypt
fixes the issue:https://www.npmjs.com/package/bcrypt#version-compatibility
The text was updated successfully, but these errors were encountered: