Running into issue when upgrading from 0.4.1->0.4.2
See original GitHub issueIf you are reporting a bug, please fill in below. Otherwise feel to remove this template entirely.
Description
Running into an error when I run npm start Error: Cannot find module ‘lru-cache’ What are you reporting? An error.
Expected behavior
The Webpack dev server to properly start. Tell us what you think should happen.
Actual behavior
Receiving the following error.
react-scripts start
module.js:327 throw err; ^
Error: Cannot find module ‘lru-cache’ at Function.Module._resolveFilename (module.js:325:15) at Function.Module._load (module.js:276:25) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at Object.<anonymous> (C:\Users\erisch\Source\Repos\Orion-Client\node_modules\react-scripts\node_modules\cross-spawn\lib\parse.js:4:11) at Module._compile (module.js:409:26) at Object.Module._extensions…js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Module.require (module.js:353:17)
Tell us what actually happens.
Environment
Run these commands in the project folder and fill in their results:
npm ls react-scripts
(if you haven’t ejected): $ npm ls react-scripts npm WARN unmet dependency C:\Users\erisch\Source\Repos\Orion-Client\node_modules\react-scripts\node_modules\extract-text-webpack-plugin requires async@‘^1.5.0’ but will load npm WARN unmet dependency C:\Users\erisch\Source\Repos\Orion-Client\node_modules\async, npm WARN unmet dependency which is version 2.0.1 npm WARN unmet dependency C:\Users\erisch\Source\Repos\Orion-Client\node_modules\react-scripts\node_modules\webpack requires async@‘^1.3.0’ but will load npm WARN unmet dependency C:\Users\erisch\Source\Repos\Orion-Client\node_modules\async, npm WARN unmet dependency which is version 2.0.1 Fortis-Client@0.0.1 C:\Users\erisch\Source\Repos\Orion-Client └── react-scripts@0.4.2node -v
: v4.4.7npm -v
: 2.15.8
Then, specify:
- Operating system: Windows 10
- Browser and version: Chrome
Reproducible Demo
Please take the time to create a new app that reproduces the issue. Unable to create a new app either. I receive the following error. $ create-react-app erik-app Creating a new React app in C:\Users\erisch\Source\Repos\erik-app.
Installing packages. This might take a couple minutes. Installing react-scripts from npm…
npm WARN optional dep failed, continuing fsevents@1.0.14 react-scripts@0.4.2 node_modules\react-scripts module.js:327 throw err; ^
Error: Cannot find module ‘graceful-fs’ at Function.Module._resolveFilename (module.js:325:15) at Function.Module._load (module.js:276:25) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at Object.<anonymous> (C:\Users\erisch\Source\Repos\erik-app\node_modules\react-scripts\node_modules\fs-extra\lib\index.js:4:11) at Module._compile (module.js:409:26) at Object.Module._extensions…js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Module.require (module.js:353:17)
Alternatively, you could copy your app that experiences the problem and start removing things until you’re left with the minimal reproducible demo.
(Accidentially, you might get to the root of your problem during that process.)
Push to GitHub and paste the link here.
By doing this, you’re helping the Create React App contributors a big time! Demonstrable issues gets fixed faster.
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (8 by maintainers)
Scratch the question I earlier asked. I’m able to create a new site and run npm start with using react-scripts 0.4.2. The issue seems isolated to npm version 2.
Thanks a bunch for the quick turnaround Dan. This library rocks!