npm ERR! could not determine executable to run

Question

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.

Did you find a fix for this? I'm stuck too. If you could add an answer that would be very helpful. — artfulrobot, Aug 27 '21 at 07:28
For those who get this error using Mikro-ORM: make sure you install mikro-orm cli `npm install --save @mikro-orm/cli` — Janac Meena, Feb 28 '22 at 20:24

score 88 · Accepted Answer · answered Nov 12 '21 at 01:28

88

Ended up doing

rm -rf .git/hooks
npm install

Followin this sugestion https://github.com/npm/cli/issues/1845#issuecomment-814884999

Worked for me

answered Nov 12 '21 at 01:28

Sr.PEDRO

1,664
19
21

2

`rm -rf .git/hooks` worked like a charm! – Reaz Murshed May 12 '22 at 09:51
Important is to use npm i. pnpm not working for that. – sunamo.cz Jul 29 '23 at 07:28

Erick Gutierrez · Answer 2 · 2021-07-28T14:13:01.397

34

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

edited Jul 28 '21 at 14:13

answered Jul 28 '21 at 13:36

Erick Gutierrez

446
3
7

1

For me, `npm install` did it. I already had husky@4 – callmekatootie Oct 11 '21 at 19:00
3

Reason why this works is that husky versions after 4 stopped installing git hooks automatically. They put up instructions how to add those here https://github.com/typicode/husky – JanBrus Feb 09 '22 at 10:36
1

for me it worked without uninstalling husky - so it may be safer this way – Evyatar Sivan May 10 '22 at 06:45

score 9 · Answer 3 · answered Jan 11 '22 at 15:58

9

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.

answered Jan 11 '22 at 15:58

shmuels

1,039
1
9
22

1

This is exactly what my issue was. Thank you for posting this. – Mauricio Martinez May 21 '22 at 02:28
Thanks for posting this. It solved my issue. – Fluffy Ribbit Jul 03 '23 at 11:09

score 8 · Answer 4 · answered Oct 28 '21 at 16:02

8

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

answered Oct 28 '21 at 16:02

RooN3y

144
1
7

score 8 · Answer 5 · answered Apr 07 '22 at 16:14

8

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

answered Apr 07 '22 at 16:14

user9083933

361
3
10

score 6 · Answer 6 · answered Dec 03 '21 at 13:51

6

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 )

answered Dec 03 '21 at 13:51

Alex

789
8
8

1

happened to me with firebase-tools. Had to downgrade node from v16 to v14 – omarwaleed Dec 28 '21 at 09:46

score 6 · Answer 7 · answered Mar 24 '22 at 14:23

6

It worked for me:

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

Sometimes its due to pre-commit hooks

answered Mar 24 '22 at 14:23

AnilS

795
1
11
15

score 3 · Answer 8 · answered Jul 20 '22 at 05:35

3

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).

answered Jul 20 '22 at 05:35

The Blind Hawk

1,199
8
24

score 2 · Answer 9 · answered Jun 23 '22 at 12:13

2

In my case, I was using npm build.

It worked after changing to npm run build.

answered Jun 23 '22 at 12:13

laplace

656
7
15

score 2 · Answer 10 · answered Sep 19 '22 at 16:01

2

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 :'(

answered Sep 19 '22 at 16:01

jgaurav6

81
4

score 1 · Answer 11 · answered Apr 17 '22 at 07:36

1

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.

answered Apr 17 '22 at 07:36

Nice Books

1,675
2
17
21

tan js · Answer 12 · 2023-03-10T15:15:01.520

1

The error found after installing cypress; opening cypress with the path works fine :

./node_modules/.bin/cypress open

edited Mar 10 '23 at 15:15

answered Nov 02 '22 at 12:44

tan js

204
2
10

score 1 · Answer 13 · answered Jun 23 '23 at 16:06

1

You can install globally the eas-cli package and the command should work.

Install it with npm:

npm install -g eas-cli

Install it with yarn:

yarn global add eas-cli

answered Jun 23 '23 at 16:06

Gonzalo

168
1
1
7

score 0 · Answer 14 · answered Nov 15 '22 at 11:24

0

npx react-native run-android npm ERR! couldn't determine execution to run this helped me to run

 npm i yarn
 yarn install

answered Nov 15 '22 at 11:24

مصطفى

555
4
9

score 0 · Answer 15 · answered Mar 20 '23 at 08:08

0

terminal was .zsh, my problem was fixed when I changed it to .bash

answered Mar 20 '23 at 08:08

birkadinyazilimci

11
1

score 0 · Answer 16 · answered Mar 29 '23 at 15:58

0

I had this problem with Expo using node 16, fixed by using node 18.

=> nvm use 18

Maybe not a proper solution, but it un-blocked me..

answered Mar 29 '23 at 15:58

Made in Moon

2,294
17
21

score -1 · Answer 17 · answered Feb 24 '22 at 07:17

-1

just use npm install then -> npm start

answered Feb 24 '22 at 07:17

Byomkesh

1
1

npm ERR! could not determine executable to run

17 Answers17

Linked