browserify / browserify/browserify
Inconsistency between browserified version and native node version
- Dominant language
- JavaScript
- Stars
- 14.7k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
I've got a relatively simple test case here that shows a simple function that produces different output when run through browserify and when run in node directly:
https://dl.dropboxusercontent.com/u/927666/test.zip
I've included the shrinkwrap, actual node_modules folder, and output of running browserify. To test you can simply compare the result of running `node index.js` with `node compiled.js`.
I previously believed this was due to a bug in crypto-browserify directly, which you can see here:
https://tonicdev.com/boucher/57193b9ee517ca11004e25ed
But I'm not so sure now, because re-running a similar test by requiring crypto-browserify directly in node produces a correct result, while the browserified version is still incorrect.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.