Open TessMyers opened 9 years ago
:+1:
Hey @TessMyers @MetaMemoryT I spoke to Shane, and he seems underwater at the minute, but gave me access to create a new npm release of bcrypt. Do you (or anyone else) want to rally some peeps together to get a new release out? Maybe something incremental? I don't want to break anyone, but it would be nice to start pushing out some things.
publishing with a bugfix version bump would be nice, and only takes a moment.
any other development necessary?
I'd say releasing a fix to point npm to correct github repo is important; people can't find the source otherwise (took me some time to find this repo).
+1
This is still broken and needs to be fixed. The link on npm is https://github.com/shaneGirish/bcryptJS when it needs to be https://www.npmjs.com/package/bcrypt-nodejs
@shaneGirish it looks like the repo link is still out of date
@joshball @shaneGirish ping
Currently:
The Github link leads to a 404. Manually adding "-nodejs" to the URL let me find the repo, but the link is currently borked. Your package.json has the right link, so you might just need to update with NPM.