Skip to content

Module not found: Can't resolve '../components/Overlay' on starting server #3041

Closed
Closed
Module not found: Can't resolve '../components/Overlay' on starting server#3041
Labels
issue: bug
Milestone
1.0.13

Description

@axelson
axelson
opened on Sep 1, 2017

Is this a bug report?

Yes

Can you also reproduce the problem with npm 4.x?

I'm using yarn 0.27.5

Which terms did you search for in User Guide?

N/A

Environment

  1. node -v: v8.2.1
  2. npm -v: 5.3.0
  3. yarn --version (if you use Yarn): 0.27.5
  4. npm ls react-scripts (if you haven’t ejected): 1.0.12

Then, specify:

  1. Operating system: Mac OS X 10.12.6
  2. Browser and version (if relevant):

Steps to Reproduce

  1. run dotenv npm run start

Expected Behavior

Server starts running.

Actual Behavior

Receive the following error:

Failed to compile.

./node_modules/react-error-overlay/lib/containers/CompileErrorContainer.js
Module not found: Can't resolve '../components/Overlay' in '/Users/jason/nob/messages-frontend-prototype/node_modules/react-error-overlay/lib/containers'

Reproducible Demo

None at the moment.

Note: Downgrading to react-scripts 1.0.11 works great.

Activity

  1. gaearon commented on Sep 1, 2017

    @gaearon
    gaearon
    on Sep 1, 2017
    Contributor

    Can you run

    rm -rf node_modules
npm i

    and try again?

  2. axelson commented on Sep 1, 2017

    @axelson
    axelson
    on Sep 1, 2017
    Author

    @gaearon That does fix the issue. But yarn upgrade react-scripts should have worked fine right?

  3. emveeoh commented on Sep 1, 2017

    @emveeoh
    emveeoh
    on Sep 1, 2017

    Also ran into this issue. Yarn install, then Yarn Start to launch Development Server. I have the same environment as the author and same error message.

    Resolution:
    Deleted the node_modules and the yarn.lock file. Yarn install, yarn start. Works perfectly now.

  4. gaearon commented on Sep 1, 2017

    @gaearon
    gaearon
    on Sep 1, 2017
    Contributor

    It's not working because the filename casing is different but OS probably didn't recognize that.
    I think we can fix it.

  5. gaearon
    added
    issue: bug
    on Sep 1, 2017
  6. gaearon
    added this to the 1.0.13 milestone on Sep 1, 2017

  7. tharakawj commented on Sep 1, 2017

    @tharakawj
    tharakawj
    on Sep 1, 2017
    Contributor

    @gaearon you mean by renaming the file to old name?

  8. gaearon commented on Sep 1, 2017

    @gaearon
    gaearon
    on Sep 1, 2017
    Contributor

    The issue is because we replaced overlay.js with Overlay.js, and FS gets confused.
    Let's just completely rename this file to something else. e.g. ErrorOverlay.js.

  9. gaearon
    closed this as completedin #3051on Sep 2, 2017

  10. himanshupathakpwd commented on Sep 2, 2017

    @himanshupathakpwd
    himanshupathakpwd
    on Sep 2, 2017

    Do,
    npm install
    or
    yarn install if you are using yarn

    It solved problem on my system

  11. gaearon
    added a commit that references this issue on Sep 2, 2017

    Changelog for 1.0.13

    e4694ab

  12. gaearon commented on Sep 2, 2017

    @gaearon
    gaearon
    on Sep 2, 2017
    Contributor

    This should be fixed in 1.0.13. Please verify.

    https://github.com/facebookincubator/create-react-app/releases/tag/v1.0.13

  13. brandonmikeska commented on Sep 3, 2017

    @brandonmikeska
    brandonmikeska
    on Sep 3, 2017

    I just upgraded to 1.0.13 and got this error when I copied and pasted yarn add --exact react-scripts@1.0.13 from the release notes.

    I went back and ran yarn upgrade react-scripts and it fixed the issue.

  14. betoharres commented on Sep 6, 2017

    @betoharres
    betoharres
    on Sep 6, 2017

    I was on 1.0.10 and then I ran yarn add --exact react-scripts@1.0.12 and yarn add --exact react-scripts@1.0.13
    both of them gave me this error. I'm trying to reinstall all modules now

    update: it works!

  15. gaearon commented on Sep 6, 2017

    @gaearon
    gaearon
    on Sep 6, 2017
    Contributor

    Yes, you'll still have the issue if you even try to upgrade to 12. That's why we recommend skipping it and going directly to 13.

    But in any case removing node_modules and reinstalling will fix it.

  16. balazsorban44 commented on Sep 6, 2017

    @balazsorban44
    balazsorban44
    on Sep 6, 2017
    Contributor

    I just tried everything posted here, and nothing works! My project was ejected with react eject. Can it be a problem? I get this error at running yarn start:

    module.js:471
    throw err;
    ^

Error: Cannot find module 'react-error-overlay/middleware'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.Module._load (module.js:417:25)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/home/balazs/github/bibic-vendeghazak/config/webpackDevServer.config.js:3:32)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/home/balazs/github/bibic-vendeghazak/scripts/start.js:32:31)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at exports._errnoException (util.js:1020:11)
    at WriteWrap.afterWrite (net.js:800:14)
error Command failed with exit code 1.

  17. nicksarafa commented on Sep 8, 2017

    @nicksarafa
    nicksarafa
    on Sep 8, 2017

    @balazsorban44 if you've already ejected perhaps try rolling back react-error-overlay to an older version.. "react-error-overlay": "^1.0.10" works for me

  18. gaearon commented on Sep 8, 2017

    @gaearon
    gaearon
    on Sep 8, 2017
    Contributor

    @balazsorban44 If you look closely at your error message, it is not the error message discussed in this thread. Please search issues for it—somebody already filed another issue about it. If you see this message it means you updated react-error-overlay to incompatible major version. Did you do this intentionally? It is expected that if you update packages to major versions, they will have breaking changes. Please don't update them if you haven't checked what changed.

  19. ankibalyan commented on Oct 1, 2017

    @ankibalyan
    ankibalyan
    on Oct 1, 2017

    After upgrading to react@16.0 this issue arises to me as well.

  20. ankibalyan commented on Oct 1, 2017

    @ankibalyan
    ankibalyan
    on Oct 1, 2017
    
module.js:491
    throw err;
    ^

Error: Cannot find module 'react-error-overlay/middleware'
    at Function.Module._resolveFilename (module.js:489:15)
    at Function.Module._load (module.js:439:25)
    at Module.require (module.js:517:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/devserve/ankServe/walkOrder/admin-panel/config/webpackDevServer.config.js:3:32)
    at Module._compile (module.js:573:30)
    at Object.Module._extensions..js (module.js:584:10)
    at Module.load (module.js:507:32)
    at tryModuleLoad (module.js:470:12)
    at Function.Module._load (module.js:462:3)
    at Module.require (module.js:517:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/devserve/ankServe/walkOrder/admin-panel/scripts/start.js:32:31)
    at Module._compile (module.js:573:30)
    at Object.Module._extensions..js (module.js:584:10)
    at Module.load (module.js:507:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! admin-panel@0.1.0 start: `node scripts/start.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the admin-panel@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/devserve/.npm/_logs/2017-10-01T18_53_03_730Z-debug.log

  21. pfftdammitchris commented on Oct 8, 2017

    @pfftdammitchris
    pfftdammitchris
    on Oct 8, 2017

    I had errors with react-error-overlay/middleware, I had upgraded them which caused errors.

    My fix was to downgrade.

    react-error-overlay to 1.0.9
    react-hot-loader to 3.0.0-beta.7

    Steps:
    yarn remove react-error-overlay -D (remove from devDependencies)
    yarn add react-error-overlay@1.0.9 -D

    yarn remove react-hot-loader -D (remove from devDependencies)
    yarn add react-hot-loader@3.0.0-beta.7

  22. deathmood commented on Oct 10, 2017

    @deathmood
    deathmood
    on Oct 10, 2017

    Having same problems on

    • Windows 10 x64
    • node 8.5.0 and 8.6.0 (tried both)
    • npm 5.3.0
    • react-scripts 1.0.13 and 1.0.14 (tried both)
    • I did not eject app

    (on macOS High Sierra works ok -- problems appears on Windows)

    image

    also

    image

    pls hlp!!!!

    ----- UPD

    to everyone having same problem: when I thought I tried everything (reinstalling node, npm, packages) someone told me to restart windows and that worked ;)

  23. zslabs commented on Oct 18, 2017

    @zslabs
    zslabs
    on Oct 18, 2017

    I've had something similar happening with a project attempting a react 16 upgrade - getting the following error:

    ./node_modules/react-error-overlay/node_modules/react-dom/lib/ReactMount.js
Module not found: Can't resolve 'react/lib/React' in '/Users/zach/Sites/rhinofront/node_modules/react-error-overlay/node_modules/react-dom/lib'

    I've tried deleting node_modules and clearing npm cache without any luck.

    Doing some research around that error (like this one) it looks like there might still be a 16 incompatibility with that module, but the package itself should support it just fine.

  24. huangsav commented on Dec 6, 2017

    @huangsav
    huangsav
    on Dec 6, 2017

    I have the same error in "react-error-overlay": "^3.0.0" with React 16.2.0
    image

  25. huangsav commented on Dec 6, 2017

    @huangsav
    huangsav
    on Dec 6, 2017

    After I re-create the whole scripts is OK.

  26. react
    locked and limited conversation to collaborators on Dec 6, 2017
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

    issue: bug

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions