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

[axelson]

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.

[gaearon]

Can you run

rm -rf node_modules
npm i

and try again?

[axelson]

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

[emveeoh]

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.

[gaearon]

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

[tharakawj]

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

[gaearon]

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.

[himanshupathakpwd]

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

It solved problem on my system

[gaearon]

This should be fixed in 1.0.13. Please verify.

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

[brandonmikeska]

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.

[betoharres]

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!