This repository was archived by the owner on Jan 26, 2019. It is now read-only.
- Notifications
You must be signed in to change notification settings - Fork 488
This repository was archived by the owner on Jan 26, 2019. It is now read-only.
Error: Cannot find module 'react-dev-utils/workspaceUtils' #320
Copy link
Copy link
Open
Description
Hi there,
Having recently upgrading to react-scripts-ts@3.0.0
due to an npm audit
which recommended the upgrade, I now get a Cannot find module
error when trying to start the server. Testing won't run either.
Audit Results:
Run
npm install react-scripts-ts@3.0.0
to resolve 80 vulnerabilities
Starting Server:
uuser@ubuntu1:/var/www/html/expired-to-be$ BROWSER=none HTTPS=true npm start
> expired-to-be@2.1.0 start /var/www/html/expired-to-be > react-scripts-ts start module.js:559 throw err; ^ Error: Cannot find module 'react-dev-utils/workspaceUtils' at Function.Module._resolveFilename (module.js:557:15) at Function.Module._load (module.js:484:25) at Module.require (module.js:606:17) at require (internal/module.js:11:18) at Object.<anonymous> (/var/www/html/expired-to-be/node_modules/react-scripts-ts/config/paths.js:14:22) at Module._compile (module.js:662:30) at Object.Module._extensions..js (module.js:673:10) at Module.load (module.js:575:32) at tryModuleLoad (module.js:515:12) at Function.Module._load (module.js:507:3) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! expired-to-be@2.1.0 start: `react-scripts-ts start` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the expired-to-be@2.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/uuser/.npm/_logs/2018-05-11T10_22_00_007Z-debug.log
-
npm ls react-scripts-ts
(if you haven’t ejected): 3.0.0 -
node -v
: 9.7.1 -
npm -v
: 6.0.1 -
Operating system: Ubuntu 16.04 x64
I've looked everywhere for a solution to this. I've gone through all the npm up && npm i
and npm i --save-dev react-dev-utils
, but can't seem to find any way to get past this error.
Thoughts?
Thanks!
kevintighe, yallie, milichev, michaeltomasik, lmorris and 1 more
Metadata
Metadata
Assignees
Labels
No labels