Skip to content

After ejecting getting "process.binding is not supported" error #815

Closed
Closed
After ejecting getting "process.binding is not supported" error#815
Labels
contributions: up for grabs!issue: bug
Milestone
0.8.2

Description

@brakowski
brakowski
opened on Oct 1, 2016

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

  1. Operating system: Linux Mint 17 Qiana
  2. Browser and version: Google Chrome 47.0.2526.111 (64-bit)
  3. Node: v6.2.1
  4. NPM: 2.11.3

    Reproducible Demo

  • create-react-app test-app
  • cd test-app
  • npm run eject
  • npm start

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

Activity

  1. amilajack commented on Oct 1, 2016

    @amilajack
    amilajack
    on Oct 1, 2016

    Try updating your npm version to the latest version

    npm cache clean
npm i -g npm

    It could have to do with how some dependencies have not been installed correctly.

  2. brakowski commented on Oct 1, 2016

    @brakowski
    brakowski
    on Oct 1, 2016
    Author

    But it works without ejecting.

    Edit: cache clean and update of npm did not solve the issue

  3. gaearon commented on Oct 1, 2016

    @gaearon
    gaearon
    on Oct 1, 2016
    Contributor

    Can you reliably reproduce it with absolutely new app?

  4. gaearon commented on Oct 1, 2016

    @gaearon
    gaearon
    on Oct 1, 2016
    Contributor

    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?

  5. brakowski commented on Oct 2, 2016

    @brakowski
    brakowski
    on Oct 2, 2016
    Author

    Yes i just now tried again. Did start the server before ejecting and it works fine, after ejecting the above mentioned error is thrown.

  6. brakowski commented on Oct 2, 2016

    @brakowski
    brakowski
    on Oct 2, 2016
    Author

    Ok found it out, adding 'url' as devDependency solves the issue.

  7. gaearon
    added
    issue: bug
    on Oct 2, 2016
  8. gaearon
    added this to the 0.7.0 milestone on Oct 2, 2016

  9. gaearon commented on Oct 2, 2016

    @gaearon
    gaearon
    on Oct 2, 2016
    Contributor

    This is weird. Our end-to-end test runs start after eject on npm 2.15.9, and Travis log seems fine.

    I also can’t reproduce it locally with npm 3, although it’s worth trying with your specific version:

    screen shot 2016-10-02 at 13 18 30

  10. gaearon commented on Oct 2, 2016

    @gaearon
    gaearon
    on Oct 2, 2016
    Contributor

    Please post output of:

    npm ls url
npm ls querystring
npm ls buffer

    after running in the ejected project in broken state.

  11. brakowski commented on Oct 2, 2016

    @brakowski
    brakowski
    on Oct 2, 2016
    Author

    npm ls url

    test-app@0.1.0 
└─┬ webpack@1.13.2
  └─┬ node-libs-browser@0.6.0
    └── url@0.10.3

    npm ls querystring

    test-app@0.1.0
└─┬ webpack@1.13.2
  └─┬ node-libs-browser@0.6.0
    └─┬ url@0.10.3
      └── querystring@0.2.0

    npm ls buffer

    test-app@0.1.0
└─┬ webpack@1.13.2
  └─┬ node-libs-browser@0.6.0
    └── buffer@4.9.1

    After installing url:

    npm ls url

    test-app@0.1.0
├── url@0.11.0 
└─┬ webpack@1.13.2
  └─┬ node-libs-browser@0.6.0
    └── url@0.10.3

    npm ls querystring

    test-app@0.1.0
├─┬ url@0.11.0
│ └── querystring@0.2.0 
└─┬ webpack@1.13.2
  └─┬ node-libs-browser@0.6.0
    └─┬ url@0.10.3
      └── querystring@0.2.0

    Buffer stays the same.

  12. gaearon commented on Oct 3, 2016

    @gaearon
    gaearon
    on Oct 3, 2016
    Contributor

    I likely won’t have time to dive into this soon, so for now please use the "add url to devDependencies" workaround.

    I would appreciate if somebody could dive into why this happens and tried to reproduce it with your npm version.

  13. gaearon
    added
    contributions: up for grabs!
    on Oct 3, 2016

  14. NessDan commented on Oct 12, 2016

    @NessDan
    NessDan
    on Oct 12, 2016

    @brakowski thank you, the url dependency fixed it.

    I was having the same issue on Ubuntu 15.10, node v6.3.1, npm v3.10.8

  15. fson
    added this to the 1.0.0 milestone on Oct 12, 2016

  16. 3 remaining items

  17. gaearon commented on Nov 30, 2016

    @gaearon
    gaearon
    on Nov 30, 2016
    Contributor

    I wonder if it's the same problem as #1023.

  20. gaearon commented on Nov 30, 2016

    @gaearon
    gaearon
    on Nov 30, 2016
    Contributor

    No, nobody has any idea why it happens.
    We really need help there.

    Yes, please cross-post because that thread is bigger.

    So far it is only reproducible on Ubuntu, never on OS X.

  22. gaearon
    modified the milestones: 0.8.2, 1.0.0 on Dec 7, 2016

  23. gaearon commented on Dec 7, 2016

    @gaearon
    gaearon
    on Dec 7, 2016
    Contributor

    Fixed in #1194.

  24. gaearon
    closed this as completedon Dec 7, 2016

  25. SkyHustle commented on Dec 7, 2016

    @SkyHustle
    SkyHustle
    on Dec 7, 2016

    I did not use create-react-app to build my project but this is the only relevant thread to my particular case. I'm using the Firebase Admin SDK and as soon as I import * as admin from 'firebase-admin' I get this same error on the client bundle.js:1048 Uncaught Error: process.binding is not supported

    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 process and what is the method binding that's being called on process? Since this is a webpack issue maybe I can require Firebase Admin SDK without the use of webpack? If so, how would I go about doing this?

  26. gaearon commented on Dec 7, 2016

    @gaearon
    gaearon
    on Dec 7, 2016
    Contributor

    @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.

  27. gaearon commented on Dec 7, 2016

    @gaearon
    gaearon
    on Dec 7, 2016
    Contributor

    Or perhaps process.binding is part of the shim (most likely) but some module you're importing assumes it's running in Node.js and relies on features not implemented by Webpack's shim.

    Are you confident https://www.npmjs.com/package/firebase-admin is supporting being run from browser environments?

  28. gaearon commented on Dec 7, 2016

    @gaearon
    gaearon
    on Dec 7, 2016
    Contributor

    Fixed in 0.8.2.
    Please verify.

    https://github.com/facebookincubator/create-react-app/releases/tag/v0.8.2

  29. Themacprod
    added a commit that references this issue on Oct 8, 2017

    Added missing node-sass and SSH2.

    aecdb72
  30. lock
    locked and limited conversation to collaborators on Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    contributions: up for grabs!issue: bug

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions