I'm working on a project in React and ran into a problem that has me stumped.
Whenever I run yarn start
I get this error:
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined
I have no idea why this is happening, if anyone has experienced this I would be grateful.
This question is related to
javascript
reactjs
redux
visual-studio-code
yarnpkg
To fix this issue simply upgrade react-scripts package (check latest version with npm info react-scripts version
):
"react-scripts": "^3.x.x"
with "react-scripts": "^3.4.1"
(or the latest available version)npm install
or yarn install
Some people reported that this issue was caused by running npm audit fix
(avoid it!).
If you have ejected, this is the proper way to fix this issue:
find this file config/webpackDevServer.config.js
and then inside this file find the following line:
app.use(noopServiceWorkerMiddleware());
You should change it to:
app.use(noopServiceWorkerMiddleware('/'));
For me(and probably most of you) the service worker is served at the root of the project. In case it's different for you, you can pass your base path instead.
I've also faced this problem and figure out it by upgrading the react-scripts
package from "react-scripts": "3.x.x"
to "react-scripts": "^3.4.1"
(or the latest available version).
node_modules\
folderpackage-lock.json
filepackage.json
file from "react-scripts": "3.x.x"
to "react-scripts": "^3.4.1"
npm i
npm start
And it works!!
Running npm i react-dev-utils@10.0.0
solved my issue.
We ejected from react-scripts
and so could not simply upgrade the package.json entry to fix this.
Instead, we did this:
1.) in a new directory, create a new project -> $> npx create-react-app foo-project
2.) and then eject it -> cd ./foo-project && npm run eject
3.) now copy the files from /foo-project/config into the config directory of our main app and fire up your dev server
hope this helps others in a similar bind.
I just had this issue after installing and removing some npm packages and spent almost 5 hours to figure out what was going on.
What I did is basically copied my src/components in a different directory, then removed all the node modules and package-lock.json (if you are running your app in the Docker container, remove images and rebuild it just to be safe); then reset it to my last commit and then put back my src/components then ran npm i
.
I hope it helps.
Simply update react-scripts to the latest version.
yarn add react-scripts@latest
OR IF USING NPM
npm install react-scripts@latest
Go to you package.json
Change "react-scripts": "3.x.x" to "react-scripts": "^3.4.0" in the dependencies
Reinstall react-scripts: npm I react-scripts
Start your project: npm start
If you have an ejected create-react-app
, I would suggest:
create-react-app
.npm run eject
or yarn eject
.package.json
.Worked for me.
I tried various approach described above but none of them worked since I have ejected my css. Finally applying following steps helped:
react-scripts
from "react-scripts": "3.x.x"
to "react-scripts": "^3.4.0"
react-dev-utils
form "react-dev-utils": "^10.x.x"
to "react-dev-utils": "10.0.0"
node-modules
folder and package-lock.json
/yarn.lock
npm install
/yarn install
If you ejected and are curious, this change on the CRA repo is what is causing the error.
To fix it, you need to apply their changes; namely, the last set of files:
Personally, I think you should manually apply the changes because, unless you have been keeping up-to-date with all the changes, you could introduce another bug to your webpack bundle (because of a dependency mismatch or something).
OR, you could do what Geo Angelopoulos suggested. It might take a while but at least your project would be in sync with the CRA repo (and get all their latest enhancements!).
In my case, it was because I (at one point) had reactn
installed, which also includes its own version of React (for some reason).
After that had been installed (even after uninstalling again), this error occured.
I simply removed node_modules
and ran npm install
again, and it worked.
Just need to remove and re-install react-scripts
To Remove
yarn remove react-scripts
To Add
yarn add react-scripts
and then rm -rf node_modules/ yarn.lock && yarn
react-scripts
version mauallyNone of the other solutions worked for me.
However, adding this to my package.json fixed the issue for me:
"resolutions": {
"react-dev-utils": "10.0.0"
},
I had the same issue running it in my pipeline.
For me, the issue was that I was using node
version v10.0.0
in my docker container.
Updating it to v14.7.0
solved it for me
Follow the below steps. I also encountered the same problem.
run command npm install npm-install
as shown in the image:
Here we go.. npm start...wao
I fixed this issue by setting a newer version of node as default in nvm i.e.:
nvm alias default 12.XX.X
I didn't want to upgrade react-scripts
, so I used the 3rd party reinstall npm module to reinstall it, and it worked.
npm i -g npm-reinstall
reinstall react-scripts
Setting the HOME environment variable to an appropriate value fix this issue for me.
Source: Stackoverflow.com