-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
process
should resolve to browser.js instead of index.js
#50
Comments
andersekdahl
added a commit
to andersekdahl/karma-common-js
that referenced
this issue
Mar 7, 2015
Don't expose Buffer by replacing use with a require call, but expose Buffer and process as real globals instead, since they are globals in Node.js. Note that this depends on these issues to be fixed: karma-runner/karma#1340 alexgorbatchev/node-browser-builtins#50
Good catch. Mind doing a PR? |
I'm on it! |
andersekdahl
added a commit
to andersekdahl/node-browser-builtins
that referenced
this issue
Mar 7, 2015
Use the browser entry point instead of the entry point for Node.js Closes alexgorbatchev#50
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently
process
is resolved with"process": require.resolve('process/')
but theprocess
package has one entry point for Node and one for browser. By usingrequire.resolve('process/')
you get the Node entry point, which doesn't work for the browser. The same fix should be applied toprocess
that is applied toos-browserify
.That is, this line:
Should be:
The text was updated successfully, but these errors were encountered: