Skip to content

Conversation

@felixrieseberg
Copy link
Contributor

  • This commit replaces bcrypt with bcrypt-node, which has the same functionality as bcrypy - except that it is a pure Node implementation. This change is required to run parse-server on Windows (one can get bcrypt to compile on Windows, but it requires a few Gigabytes of dependencies).

@felixrieseberg felixrieseberg changed the title 🏁 Add Windows Support (bcrypt > bcrypt-node) Add Windows Support (bcrypt > bcrypt-node) Feb 1, 2016
@gfosco
Copy link
Contributor

gfosco commented Feb 1, 2016

I see bcrypt-nodejs and bcrypt-node by the same author, but bcrypt-nodejs has a lot more usage activity... Should we be using that instead?

@felixrieseberg
Copy link
Contributor Author

Good point - going with bcrypt-nodejs might be the more popular choice. We at Microsoft did a quick check, either one would allow peeps to run this without any worries (I believe they're both using bcrypt.js underneath). I updated they PR.

crypto.js Outdated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missed changing this one

- This commit replaces bcrypt with bcrypt-node, which has the same functionality as bcrypy - except that it is a pure Node implementation. This change is required to run parse-server on Windows (one can get bcrypt to compile on Windows, but it requires a few Gigabytes of dependencies).
@felixrieseberg
Copy link
Contributor Author

@gfosco: Thanks for the catch.

gfosco added a commit that referenced this pull request Feb 1, 2016
Add Windows Support (bcrypt > bcrypt-node)
@gfosco gfosco merged commit 7f01a67 into parse-community:master Feb 1, 2016
@gfosco
Copy link
Contributor

gfosco commented Feb 1, 2016

👍

@fabiocav
Copy link

fabiocav commented Feb 1, 2016

@gfosco do you have plans to release an update to npm soon? Would be great to have this change published!

@gfosco
Copy link
Contributor

gfosco commented Feb 1, 2016

Yeah, but some tests are failing right now.... Once I fix it will release a new version.

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

Successfully merging this pull request may close these issues.

3 participants