-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
After ejecting getting "process.binding is not supported" error #815
Comments
Try updating your npm version to the latest version
It could have to do with how some dependencies have not been installed correctly. |
But it works without ejecting. Edit: cache clean and update of npm did not solve the issue |
Can you reliably reproduce it with absolutely new app? |
Okay, this stack trace is super valuable. Looks like this has something to do with webpackHotDevClient pulling in url pulling in querystring pulling in some sort of broken Buffer polyfill. Can anybody else reproduce this? |
Yes i just now tried again. Did start the server before ejecting and it works fine, after ejecting the above mentioned error is thrown. |
Ok found it out, adding 'url' as devDependency solves the issue. |
This is weird. Our end-to-end test runs I also can’t reproduce it locally with npm 3, although it’s worth trying with your specific version: |
Please post output of:
after running in the ejected project in broken state. |
npm ls url npm ls querystring
npm ls buffer After installing url:npm ls url
npm ls querystring
Buffer stays the same. |
I likely won’t have time to dive into this soon, so for now please use the "add I would appreciate if somebody could dive into why this happens and tried to reproduce it with your npm version. |
@brakowski thank you, the I was having the same issue on Ubuntu 15.10, node v6.3.1, npm v3.10.8 |
I have same issue, but the url dependency did not solve the issue... npm ls url
npm ls querystring
npm ls buffer
i have this issue with this computer, and a computer's coworker on ubuntu. |
I experienced this issue and mistakenly attributed it to a module I was using. My project was not ejected. See: rjsf-team/react-jsonschema-form#321 My workaround was to build my app inside a disposable container. |
I wonder if it's the same problem as #1023. |
I am experiencing this same error message after installing a different module, auth0-lock (https://github.com/auth0/lock). I have not ejected my project, but I found others were experiencing the same error message, such as @sirreal , and as mentioned at #587. I saw that this issue is still open, while those other ones are closed, so I've decided to post about my experience here. npm: 3.10.8 I ran
Thought I'd post in case these are all related and it could help fix this issue! ¯_(ツ)_/¯ |
@gaearon Should I post my message above in #1023? Or do y'all have a pretty good idea what's going on already? I scanned that issue, but it's a bit above my head ;P. Also, it may be worth noting that just requiring auth0-lock module breaks it. Finally, I'm in a room of 12 people and everyone else has a Mac and are not running into this issue. |
No, nobody has any idea why it happens. Yes, please cross-post because that thread is bigger. So far it is only reproducible on Ubuntu, never on OS X. |
Fixed in #1194. |
I did not use I've tried everything in this thread and it still won't go away, any insight would be appreciated!? I'm kinda desperate at this point :( Could someone at least explain what exactly is |
@Dmitry1007 Have you seen my summary in #1194 (comment)? This likely means a Node.js module somehow ends up in your build instead of Webpack's shim. |
Or perhaps Are you confident https://www.npmjs.com/package/firebase-admin is supporting being run from browser environments? |
Fixed in 0.8.2. https://github.com/facebookincubator/create-react-app/releases/tag/v0.8.2 |
Get process bnding error with line "ssh2 = require("ssh2") Check with facebook/create-react-app#815
Description
After ejecting a newly created app, and try to open it in the browser, i get a "Uncaught Error: process.binding is not supported" in the browser.
Expected behavior
It should work the same like before ejecting.
Actual behavior
An "Uncaught Error: process.binding is not supported" error is displayed in the browser console.
Environment
Reproducible Demo
Seems like "usr/lib/nodejs" is also bundled by webpack. The whole error message:
Uncaught Error: process.binding is not supportedprocess.binding
@ browser.js:173(anonymous function)
@ buffer.js:4(anonymous function)
@ buffer.js:1293__webpack_require__
@ bootstrap e7633f287f581d8681cb:555fn
@ bootstrap e7633f287f581d8681cb:86(anonymous function)
@ querystring.js:6__webpack_require__
@ bootstrap e7633f287f581d8681cb:555fn
@ bootstrap e7633f287f581d8681cb:86(anonymous function)
@ url.js:61__webpack_require__
@ bootstrap e7633f287f581d8681cb:555fn
@ bootstrap e7633f287f581d8681cb:86(anonymous function)
@ webpackHotDevClient.js:22__webpack_require__
@ bootstrap e7633f287f581d8681cb:555fn
@ bootstrap e7633f287f581d8681cb:86(anonymous function)
@ bootstrap e7633f287f581d8681cb:578__webpack_require__
@ bootstrap e7633f287f581d8681cb:555(anonymous function)
@ bootstrap e7633f287f581d8681cb:578(anonymous function)
@ bootstrap e7633f287f581d8681cb:578
The text was updated successfully, but these errors were encountered: