Create-react-app: Cannot find module './full-chrome-versions'

[morriq]

Description

What are you reporting?
I started with egghead course: https://egghead.io/lessons/react-react-fundamentals-development-environment-setup and i failed on initial step...

it's 'pure' instalation and aplication
npm start/yarn start not works as it should. It shows:
`Failed to compile.

Error in ./src/index.js
Module build failed: Error: Cannot find module './full-chrome-versions' (While processing preset: "/www/sites/react/wwwroot/node_modules/babel-preset-env/lib/index.js") (While processing preset: "/www/sites/react/wwwroot/node_modules/babel-preset-react-app/index.js")
@ multi main`

Expected behavior

npm start should work

Actual behavior

npm start not working

Environment

Run these commands in the project folder and fill in their results:

1. npm ls react-scripts (if you haven’t ejected):
2. node -v: 6.5.0
3. npm -v: 4.4.4

Then, specify:

1. Operating system: osx
2. Browser and version: chrome 57

[keithmooredev]

After updating to latest npm (4.4.4), I had to rm -rf ~/.npm/create-react-app, re-install create-react-app globally, and then generate a new create-react-app app. Got a bunch of warnings about unmet peer dependencies, which I ignored. Then npm start worked.

Merely removing the project's node_modules folder and running npm install did NOT work.

[mvanlonden]

Still doesn't work for me @kdavidmoore. https://github.com/facebookincubator/create-react-app/issues/1901

[teophilus]

Experiencing the same error with a brand new app build, however a build I made earlier this week works fine.

[kieferhagin]

Having the same issue with existing ejected installations after clearing out node_modules (existing builds with intact node_modules work as expected).

node -v: v7.7.2
npm -v: 4.4.4

[kieferhagin]

Can confirm now fixed for me (ejected) after clearing node_modules and a fresh npm i #1901

[teophilus]

@mvanlonden in your create-react-app directory run rm -r node_modules/ then run npm i this fixed it for me.

[Timer]

Thanks for the report, unfortunately this is not a bug with CRA and instead with a dependency you are using.

The issue, however, seems to have been fixed by the package causing this (https://github.com/Kilian/electron-to-chromium) (thanks for the tip @existentialism).
Please follow the instructions suggested by other members by performing a complete reinstall of your node modules.

[mvanlonden]

Ah it's working now. Had to clear npm cache