npm ERR! could not determine executable to run

Viewed 65991

I wanna run my project by npm run watch and when I do nothing, it suddenly appears an error like this.

git:(master) ✗ npm run watch

> watch
> npx mix watch

npm ERR! could not determine executable to run

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/bintangtobing/.npm/_logs/2021-06-04T08_11_16_499Z-debug.log

Does anyone know about these errors?

I have already did a solution, it is

delete node_modules on the project folder and run an npm install and it still got the same error.

Can anyone help me, please? Thank you, everyone.

12 Answers

It worked for me:

npm uninstall husky && npm install --save-dev husky@4

It happens because git is trying to find a file that doesn't exist (in version 5) so downgrading helps, I know that's not the best solution but could help someone.

Or try to migrate husky (4 to 7):

https://github.com/typicode/husky-4-to-7

npm install

I had this problem after trying to debug a build issue. I deleted the node_modules and ran the app in a docker container. But this meant the husky npm package wasn't available locally anymore so a simple npm install fixed the problem

I had to downgrade node from v17.0.1 to v14.18.1, because newer node-version was not supported by one of my project's dependencies.

( e.g. via "nvm use 14", see Node Version Manager )

My issue was is that I was mistakenly calling npx start instead of npm start.

I was doing this from the CMD line in my Dockerfile.

I realize this isn't the OPs question, but the error and title may bring others here who are getting this error.

In my case i was using wrong cmd . npx create react-app assignment

cmd should be like npx create-react-app my-project

mistake : I was missing "-" in between create and react in cmd

It worked for me:

git commit -m "updating the dependency packages" --no-verify

Sometimes its due to pre-commit hooks

In my case, I was using npm build.

It worked after changing to npm run build.

I had tried installing npm in a repo that didn't need it, and the installation had failed, therefore

rm -rf .git/hooks

without using

npm install

worked for me (because npm install would fail again).

npm audit fixed the issue for me while trying to run, npx ng n <folder-name>.

Angular was installed locally in this folder, which already contained an Angular project.

I was stuck on this error for a while. Very obvious, but I was simply running an invalid npx command. The message by itself wasn't very helpful and it took me quite some time to figure that out :'(

just use npm install then -> npm start

Related