Issue with 'crypto' Module

Hey,

I’m currently using the ccxt library with a Meteor application I’m developing - it’s a brilliant library and has been a great help, so thank you! The issue is the use of Node’s crypto module, which causes confusion with NPM over an old, deprecated package of the same name, from what I gather. As a result I get a conflict error when compiling my app.

Uncaught Error: Cannot find module 'crypto'

I can bypass the issue during development by simply deleting the deprecated crypto module from my node_modules folder, however when I go to deploy I don’t have control over this. Do you know anyway around this, or would it be possible to implement another cryptographic module like crypto-js? Or is the only option to fork & make the ammendment myself?

Thanks for any advice you can offer.

[kroitor]

Yeah, I think I will rewrite the Node.js HMAC/hash code to crypto-js (aka CryptoJS). It is already used for browser-specific ccxt implementation, so I will also switch to it under Node as well. I’ll update you on the progress, should be ready by tomorrow (if nothing extraordinary comes up).

[x5engine]

indeed well done and module crypto is ugly!