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
At the very least, the test suite is bailing in Testling with:
not ok 1 Error: Uncaught TypeError: Object #<Object> has no method 'pseudoRandomBytes' on line 7540
However, the test suite will not work as-is in the browser at all, because it is trying to compare the result of the crypto-browserify version in the repo against what require('crypto') pulls in. Which, after running the test suite through browserify, is actually just the previous (or even current!) version of crypto-browserify.
The test suite needs to precompile the results of all hashes and hmacs to a file that can be used for comparisons without relying on running node's crypto module during the tests. The sha.js module is doing that correctly.
The text was updated successfully, but these errors were encountered:
crypto-browserify is moving away from being an implementation to just bundling modules to get the same api as crypto. we should probably still have tests, but they can be much simpler, and maybe run the tests from the modules.
At the very least, the test suite is bailing in Testling with:
However, the test suite will not work as-is in the browser at all, because it is trying to compare the result of the
crypto-browserify
version in the repo against whatrequire('crypto')
pulls in. Which, after running the test suite through browserify, is actually just the previous (or even current!) version ofcrypto-browserify
.The test suite needs to precompile the results of all hashes and hmacs to a file that can be used for comparisons without relying on running node's
crypto
module during the tests. Thesha.js
module is doing that correctly.The text was updated successfully, but these errors were encountered: