Hash result is different from scrypt library. about node-js-scrypt

[tracker1]

Looks like the upstream version I used in my copy had an incompatibility with the current one...

https://github.com/tonyg/js-scrypt/commits/master/browser/scrypt.js
https://github.com/tonyg/js-scrypt/

Again, more than open to suggestions on a library to wrap around the same interface... though, should also consider the newer worker in node 11.7 as well as a Promise based interface.

[tracker1]

I didn't write the underlying js-script, it was copied from an asm compiled version about 6 years ago... so I cannot really comment on that aspect, all I did at that time was write wrappers so that I could at least run a few instances in the background in node via a pool of connected workers.

I should probably just deprecate the package in npm and point to one of the other versions... IIRC, when I wrote it, my results were matching a .Net implementation...

Do you have one you would recommend over the others?

[tracker1]

Aside, I don't know that I should fix it.. if anyone is using this library currently, I could maybe bump the full version with a NOTE and make this just a wrapper against one of the other libraries you're referencing.

[novemberde]

@tracker1 Thank you for your answer.

I found the difference among that libraries. Each library has different function parameter.
Actually, I'd aliased js-scrypt instead of scrypt for making a bundle using webpack, so I found it returns different hash result.

Now, I include 'scrypt' on webpack bundling, it works well!
All is fine.

Thank you again :)