create-react-app: Module not found: Can't resolve '../components/Overlay' on starting server

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.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 21 (8 by maintainers)

Commits related to this issue

Most upvoted comments

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.

Can you run

rm -rf node_modules
npm i

and try again?

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

@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

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.


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

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.

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