React npm start not working : 'No version of chokidar available'

Question

I cloned my already working React-Typescript app on Github Pages, from Github and wanted to make some changes. I ran npm install and installed all the dependencies but when I run npm start, I got this error;

I don't know what chokidar is and I looked a little bit and I think it's unrelated to my project. Still I tried to npm install chokidar and I got another error like this;

Also tried npm audit fix as well. Fixed some stuff but nothing changed.

So I can't open the development server. Additionally, this is the package.json file;

// package.json
{
  "name": "panflix",
  "homepage": "https://absolutezero13.github.io/meerkast/",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "@testing-library/jest-dom": "^5.11.4",
    "@testing-library/react": "^11.1.0",
    "@testing-library/user-event": "^12.1.10",
    "@types/enzyme": "^3.10.8",
    "@types/jest": "^26.0.15",
    "@types/node": "^12.0.0",
    "@types/react": "^17.0.0",
    "@types/react-dom": "^17.0.0",
    "@types/redux-devtools": "^3.0.47",
    "axios": "^0.21.1",
    "enzyme": "^3.11.0",
    "firebase": "^8.2.7",
    "gh-pages": "^3.1.0",
    "history": "^4.10.1",
    "react": "^17.0.1",
    "react-bootstrap": "^1.5.0",
    "react-dom": "^17.0.1",
    "react-redux": "^7.2.2",
    "react-router-dom": "^5.2.0",
    "react-scripts": "4.0.2",
    "redux": "^4.0.5",
    "redux-devtools-extension": "^2.13.8",
    "redux-thunk": "^2.3.0",
    "typescript": "^4.1.2",
    "web-vitals": "^1.0.1"
  },
  "scripts": {
    "predeploy": "npm run build",
    "deploy": "gh-pages -d build",
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": [
      "react-app",
      "react-app/jest"
    ]
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  },
  "devDependencies": {
    "@types/react-redux": "^7.1.16",
    "@types/react-router-dom": "^5.1.7"
  }
}

I tried npm install -g chokidar and it is installed. But I'm getting the same error as before "no version chokidar is available."

Other react projects are working fine.

Maybe this can help stackoverflow.com/a/56105431/9095807
– Girgetto
Commented Mar 21, 2021 at 16:57 — Girgetto, Commented Mar 21, 2021 at 16:57

dieselcz · Accepted Answer · 2021-03-30 07:37:56Z

37

I had the same issue. What worked for me is forcing updates on local npm packages:

npm update --force

Before

$ npm list chokidar
[email protected]
└─┬ [email protected]
  └─┬ [email protected]
    └── [email protected]

After

$ npm list chokidar
[email protected]
└─┬ [email protected]
  ├─┬ [email protected]
  │ └── [email protected]
  └─┬ [email protected]
    └─┬ [email protected]
      ├── [email protected]
      └─┬ [email protected]
        └── [email protected]

Update

We found that NPM 7 was the issue. Downgrading to NPM 6.14.12 works without any changes.

edited Mar 30, 2021 at 7:37

answered Mar 29, 2021 at 8:51

dieselcz

4333 silver badges10 bronze badges

2

Downgrading works, but there is no need. You can just npm update chokidar. See my answer below. Also force update might not be a good idea to update all the dependencies if you have not specified the exact version of the dependency.
– Shnigi
Commented Oct 5, 2021 at 10:14

Add a comment |

Shnigi · Accepted Answer · 2022-02-25 08:42:57Z

32

Just solved my issue by running

npm update chokidar

This will update the package-lock.json with latest chokidar info. Now running react without any issues with npm 7.15 and node 14.16. There is no need to force install or do anything quirky. Just update chokidar to keep your package files consistent and keep development running for everyone in the team.

Original problem came up when I updated from NPM 6 to version 7. There is also a bug ticket in github: https://github.com/facebook/create-react-app/issues/10811

edited Feb 25, 2022 at 8:42

answered May 28, 2021 at 12:54

Shnigi

1,00210 silver badges19 bronze badges

This solution is the simplest working for me so far, thanks! Resolve the exact same issue on a CRA app just updated to npm 7.
– Soullivaneuh
Commented Jun 16, 2021 at 13:42
This solution solved all of my issues, thank you!
– Juha Tauriainen
Commented Jun 30, 2021 at 8:34

Add a comment |

Ardeshir Izadi · Accepted Answer · 2021-08-04 06:48:37Z

16

The same problem occurred to me after upgrading from [email protected] to [email protected]. I solved my problem with simply installing chokidar as a DevDependency. Everything works as expected (development, production build and tests)

For more assurance run:

npm i -g npm
npm cache verify
npm i -D chokidar
npm i

edited Aug 4, 2021 at 6:48

answered Apr 3, 2021 at 8:48

Ardeshir Izadi

1,0451 gold badge8 silver badges26 bronze badges

2

It seems to be enough to just update chokidar with npm update chokidar. One command needed at least for me =)
– Shnigi
Commented Jun 3, 2021 at 6:18
That is nice. Does it work with pure clone? e.g. rm -rf node_modules; npm i ; npm start ?
– Ardeshir Izadi
Commented Jun 3, 2021 at 11:10
1

probably not if you have not updated you package-lock file. Then just rm -rf node_modules; npm i ; npm update chokidar; npm start
– Shnigi
Commented Jun 4, 2021 at 7:37
Aha. nice. I just asked to make sure other teammates would then be able to benefit just from a simple npm i
– Ardeshir Izadi
Commented Jun 4, 2021 at 10:33
Your teammates can just npm i if you first update the package lock file and push it to the repository for everybody.
– Shnigi
Commented Jun 16, 2021 at 8:13

Add a comment |

Xhafer Durmishi · Accepted Answer · 2021-04-02 07:52:29Z

5

Chockidar is a dependency inside watchpak which takes care of hot reloads on save on development environment.

Chuckidar 2 has problems with node v14+.

For me, npm update did update watchpack to use chockidar 3.

answered Apr 2, 2021 at 7:52

Xhafer Durmishi

512 bronze badges

Add a comment |

Kshitiz Vatsa · Accepted Answer · 2021-07-29 18:17:04Z

It is because the version of chokidar NEEDS to be updated to 3

Method 1:

npm i chokidar@latest --force

This worked for me. npm itself says : npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.

Method 2(Recommended):

npm audit fix

If you are connecting via proxy on company network this might not work for you and you could get something like this:

npm ERR! audit endpoint returned an error

Method 3:

Downgrade npm version to 6

Method 4:

npm update --force

Would not recommended for large projects.

Malek Zarzour · Accepted Answer · 2021-07-02 08:37:56Z

3

Updating Chokidar dependency solved the problem for me.

npm update chokidar

answered Jul 2, 2021 at 8:37

Malek Zarzour

694 bronze badges

Add a comment |

vineet tanwar · Accepted Answer · 2021-07-13 07:59:20Z

You needs to update chokidar. So simply needs to hit the command npm update chokidar OR npm update chokidar@2

if you gets error like as invalid json response body at https://registry.npmjs.org/chokidar reason: Unexpected end of JSON input

Then main reason for it may be cache, so you have to clean cache. For that, hit the command npm cache clean --force

After this, if you again gets one more error like as

 `ENOENT: no such file or directory, scandir '/node_modules/node-sass/vendor'`

Then you needs to rebuild node sass, by hitting the command npm rebuild node-sass

That's all, how it worked for me.

Jatniel · Accepted Answer · 2023-01-04 17:57:16Z

1

This command will fix your problem :

$ npm update chokidar

I got this problem also when I'm cloning project and installing npm

edited Jan 4, 2023 at 17:57

Jatniel

2,6623 gold badges21 silver badges33 bronze badges

answered Jan 4, 2023 at 6:29

0MUHAMMEDIRFAN

5110 bronze badges

1

Welcome to SO. Though we thank you for your answer, it would be better if it provided additional value on top of the other answers. In this case, your answer does not provide additional value, since another user already posted that solution. If a previous answer was helpful to you, you should vote it up once you have enough reputation
– Mark Ormesher
Commented Jan 5, 2023 at 8:31

Add a comment |

Mohammad Mohammadi · Accepted Answer · 2021-12-10 08:18:22Z

0

I got this problem today I search everywhere, and then fix my problem with this:

$ npm update --force

answered Dec 10, 2021 at 8:18

Mohammad Mohammadi

3054 silver badges11 bronze badges

Add a comment |

fgamess · Accepted Answer · 2022-12-13 05:04:10Z

0

I'm on Centos7 and my Chokidar version is "^3.5.3".

My issue was resolved by running this command:

npm update --force

edited Dec 13, 2022 at 5:04

fgamess

1,3082 gold badges13 silver badges25 bronze badges

answered Dec 7, 2022 at 15:01

user210912

112 silver badges4 bronze badges

Add a comment |

Collectives™ on Stack Overflow

React npm start not working : 'No version of chokidar available'

10 Answers 10

Before

After

Update

Not the answer you're looking for? Browse other questions tagged
reactjs
typescript
npm
chokidar
or ask your own question.

Linked

Hot Network Questions

Collectives™ on Stack Overflow

10 Answers 10

Before

After

Update

Not the answer you're looking for? Browse other questions tagged reactjstypescriptnpmchokidar or ask your own question.

Linked

Related

Not the answer you're looking for? Browse other questions tagged
reactjs
typescript
npm
chokidar
or ask your own question.