Error could not determine executable to run

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.

asked Jun 4, 2021 at 8:16

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, 2021 at 16:02

It worked for me:

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

Sometimes its due to pre-commit hooks

answered Mar 24, 2022 at 14:23

In my case, I was using npm build.

It worked after changing to npm run build.

answered Jun 23, 2022 at 12:13

answered Sep 19, 2022 at 16:01

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, 2022 at 7:36

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, 2022 at 5:35

Error after installing cypress, ppening cypress with path works fine:

./node_modules/.bin/cypress open

answered Nov 2, 2022 at 12:44

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, 2022 at 11:24

answered Feb 24, 2022 at 7:17

This might be related to #1834

@rafgraph On windows, I had no issues for hooks to be installed with Husky. When I used WSL on Ubuntu though, I had to use sudo for hooks to be installed, otherwise I had errors in the npm install log. So I don’t think this is strictly related, since the error above can be reproduced by simply running npx husky-run pre-commit without hooks being installed at all.

@csvn can you try installing the latest beta & seeing if you can repro? npm i -g npm@next-7. If you’re still experiencing this, we’d love the debug.log

Hi @darcyclarke. Attached the output for the debug.log for the reproduction steps in the description.

0 verbose cli [
0 verbose cli   '/usr/local/bin/node',
0 verbose cli   '/usr/local/share/npm-global/lib/node_modules/npm/bin/npm-cli.js',
0 verbose cli   'exec',
0 verbose cli   '--',
0 verbose cli   'husky-run',
0 verbose cli   'pre-commit'
0 verbose cli ]
1 info using npm@7.0.0-beta.12
2 info using node@v14.10.1
3 timing config:load:defaults Completed in 2ms
4 timing config:load:file:/usr/local/share/npm-global/lib/node_modules/npm/npmrc Completed in 1ms
5 timing config:load:builtin Completed in 1ms
6 timing config:load:cli Completed in 1ms
7 timing config:load:env Completed in 0ms
8 timing config:load:file:/workspaces/npm-husky-test/.npmrc Completed in 0ms
9 timing config:load:project Completed in 1ms
10 timing config:load:file:/root/.npmrc Completed in 0ms
11 timing config:load:user Completed in 0ms
12 timing config:load:file:/usr/local/etc/npmrc Completed in 1ms
13 timing config:load:global Completed in 1ms
14 timing config:load:cafile Completed in 0ms
15 timing config:load:validate Completed in 0ms
16 timing config:load:setEnvs Completed in 1ms
17 timing config:load Completed in 7ms
18 verbose npm-session 53798df1482fef51
19 timing npm:load Completed in 13ms
20 http fetch GET 200 https://registry.npmjs.org/husky-run 832ms
21 timing command:exec Completed in 840ms
22 verbose stack Error: could not determine executable to run
22 verbose stack     at getBinFromManifest (/usr/local/share/npm-global/lib/node_modules/npm/lib/exec.js:210:23)
22 verbose stack     at exec (/usr/local/share/npm-global/lib/node_modules/npm/lib/exec.js:98:15)
23 verbose cwd /workspaces/npm-husky-test
24 verbose Linux 4.19.128-microsoft-standard
25 verbose argv "/usr/local/bin/node" "/usr/local/share/npm-global/lib/node_modules/npm/bin/npm-cli.js" "exec" "--" "husky-run" "pre-commit"
26 verbose node v14.10.1
27 verbose npm  v7.0.0-beta.12
28 error could not determine executable to run
29 verbose exit 1

I ran this within a Docker Devcontainer and WSL in VSCode. Environment info:

root@cc760b824422:/workspaces/npm-husky-test# npm -v
7.0.0-beta.12
root@cc760b824422:/workspaces/npm-husky-test# node -v
v14.10.1

This is the same for Windows, npm 7.0.0-beta.12 node v14.8.0:

0 verbose cli [
0 verbose cli   'C:\Program Files\nodejs\node.exe',
0 verbose cli   'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
0 verbose cli   'exec',
0 verbose cli   '--',
0 verbose cli   'husky-run',
0 verbose cli   'pre-commit'
0 verbose cli ]
1 info using npm@7.0.0-beta.12
2 info using node@v14.8.0
3 timing config:load:defaults Completed in 1ms
4 timing config:load:file:C:Program Filesnodejsnode_modulesnpmnpmrc Completed in 0ms
5 timing config:load:builtin Completed in 0ms
6 timing config:load:cli Completed in 1ms
7 timing config:load:env Completed in 1ms
8 timing config:load:file:C:UsersChristianDev@apptusesales-fashion.npmrc Completed in 1ms
9 timing config:load:project Completed in 1ms
10 timing config:load:file:C:UsersChristian.npmrc Completed in 1ms
11 timing config:load:user Completed in 1ms
12 timing config:load:file:C:Program Filesnodejsetcnpmrc Completed in 0ms
13 timing config:load:global Completed in 0ms
14 timing config:load:cafile Completed in 0ms
15 timing config:load:validate Completed in 0ms
16 timing config:load:setEnvs Completed in 1ms
17 timing config:load Completed in 6ms
18 verbose npm-session 3e0f43b059d2f137
19 timing npm:load Completed in 15ms
20 http fetch GET 200 https://registry.npmjs.org/husky-run 85ms
21 timing command:exec Completed in 95ms
22 verbose stack Error: could not determine executable to run
22 verbose stack     at getBinFromManifest (C:Program Filesnodejsnode_modulesnpmlibexec.js:210:23)
22 verbose stack     at exec (C:Program Filesnodejsnode_modulesnpmlibexec.js:98:15)
23 verbose cwd C:UsersChristianDev@apptusesales-fashion
24 verbose Windows_NT 10.0.19041
25 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "exec" "--" "husky-run" "pre-commit"
26 verbose node v14.8.0
27 verbose npm  v7.0.0-beta.12
28 error could not determine executable to run
29 verbose exit 1

the issue here is that npx thinks you’re trying to run husky-run the package rather than husky-run the bin script that’s part of husky.

what you’ll want to do to run the husky-run script within husky itself, is

which informs npx which package contains the bin, and I can confirm works correctly

I get this same error could not determine executable to run when running husky as a pre-commit hook. Error log attached.

2020-10-02T00_36_01_041Z-debug.log

husky was installed with npm v6 (because of #1834), the pre-commit hook successfully setup. It is setup in package.json to run lint-staged as described in prettier docs. This works fine with npm v6

  "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  "lint-staged": {
    "src/**/*": "prettier --write --ignore-unknown"
  }

@nlf running npx husky-run is just for illustrating the problem. The real issue is that the hooks running with Husky fails when Husky executes them. So it is really the package that needs updating, if this issue is «working as intended». npx with npm v6 managed to find /node_modules/.bin/husky-run and run correctly. So this is a breaking change, and I was just curious if this is intended.

So in my mind, there are two options:

• Ensure that npx <command> can find scripts in /node_modules/.bin if they match first
• Update Husky so that it works with npm v7

I just wanted clarity which option is the right one, before opening an issue on Husky with this.

To add another data point, I think I’m running into the same issue with the vue-cli-service bin script (which works in npm@6).

$ npx vue-cli-service serve
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/vue-cli-service - Not found
npm ERR! 404
npm ERR! 404  'vue-cli-service@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

$ npx vue serve
npm ERR! could not determine executable to run

Based on nlf’s comment there is a workaround until this is fixed in npm@7:

$ npx -p @vue/cli-service vue-cli-service serve

we published v7.0.0-rc.4 today that restores the old behavior of npx with regards to already installed scripts and should resolve these issues.

you can update with npm i -g npm@next-7 and let us know how it goes!

Thanks @nlf! I can verify that my Husky hooks now works again, same as with npm v6.

Hi @nlf i still got error using npm v7.4.0

please open a new issue and be sure to fill out the template and i’ll see if i can help figure out what’s going on

Can confirm behaviour is working in 7.5.2 however I had to run npm rebuild to re-install husky’s hooks. This may be helpful for you @hanifmhd

I got this issue with npx postcss and fixed it by removing the dist directory and running npx postcss again.

I ran into the same bug after upgrading husky from version 4 to 5.

Installing new version of package wasn’t enough. The solution to fix this issue was to migrate husky to newer version.
There’s a helpful tool for this task: https://github.com/typicode/husky-4-to-5

the issue here is that npx thinks you’re trying to run husky-run the package rather than husky-run the bin script that’s part of husky.

what you’ll want to do to run the husky-run script within husky itself, is

which informs npx which package contains the bin, and I can confirm works correctly

Hi there,

I hope I’m not making a mistake by posting here but the quoted answer is for me the closest to a solution.

I’m pretty sure you got that right because if I check the log it said «http fetch GET 304 https://registry.npmjs.org/husky-run 201ms» so I reckon it is looking for a package instead of running the script.

But I’m using Nuxt and I’m not sure how I can fix this as the solution offered is for the npm cli. If anyone has an idea it will be really appreciated.

Thanks!

EDIT : after more research, I found this StackOverFlow thread : https://stackoverflow.com/questions/66246587/how-to-fix-error-not-found-husky-run-when-committing-new-code
So I tried :

rm -rf .git/hooks
npm install

Seems to work OK now. 👍

@nlf running npx husky-run is just for illustrating the problem. The real issue is that the hooks running with Husky fails when Husky executes them. So it is really the package that needs updating, if this issue is «working as intended». npx with npm v6 managed to find /node_modules/.bin/husky-run and run correctly. So this is a breaking change, and I was just curious if this is intended.

So in my mind, there are two options:

• Ensure that npx <command> can find scripts in /node_modules/.bin if they match first
• Update Husky so that it works with npm v7

I just wanted clarity which option is the right one, before opening an issue on Husky with this.

This was my issue! I had recently moved to a new machine and had forgotten to re-install npx.

#while create new react app i am fcaing this issue

i have tried all command given above.

——>npx install create-react-app zoho

after given above cmd . i am facing below error

npm ERR! could not determine executable to run

npm ERR! A complete log of this run can be found in:
npm ERR! C:UsersAdminAppDataLocalnpm-cache_logs2021-06-08T02_41_23_166Z-debug.log

I used npx tsc —init. Worked for me. Im on a linux machine, if that fact matters. I also have typescript installed globally with npm.

the issue here is that npx thinks you’re trying to run husky-run the package rather than husky-run the bin script that’s part of husky.
what you’ll want to do to run the husky-run script within husky itself, is

which informs npx which package contains the bin, and I can confirm works correctly

Hi there,

I hope I’m not making a mistake by posting here but the quoted answer is for me the closest to a solution.

I’m pretty sure you got that right because if I check the log it said «http fetch GET 304 https://registry.npmjs.org/husky-run 201ms» so I reckon it is looking for a package instead of running the script.

But I’m using Nuxt and I’m not sure how I can fix this as the solution offered is for the npm cli. If anyone has an idea it will be really appreciated.

Thanks!

EDIT : after more research, I found this StackOverFlow thread : https://stackoverflow.com/questions/66246587/how-to-fix-error-not-found-husky-run-when-committing-new-code
So I tried :

rm -rf .git/hooks
npm install

Seems to work OK now. 👍

This is NOT a good way to fix it.

In fact you will completely remove all git hooks you have setup, so naturally there will be nothing to run and thus it will produce no error.

Doesn’t that indicate the problem is the hooks themselves, and not npm?

Add "prepare": "husky install" as a script to package.json to fix it for everyone else when they will run npm install, then run npm run prepare to fix if for yourself.

( Note: this is done automatically for you when using the migration script here : https://github.com/typicode/husky-4-to-7 )

npm i yarn
yarn install
then run command again npx husky-run pre-commit

It worked for me:

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

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

Or try to migrate husky (4 to 7):

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

Ended up doing

rm -rf .git/hooks
npm install

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

Worked for me

npm install

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

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

( e.g. via «nvm use 14», see Node post uvdos node.js Version Manager )

My issue was is that I was mistakenly post uvdos node.js calling npx start instead of npm start.

I was doing this from the CMD line in my post uvdos node.js Dockerfile.

I realize this isn’t the OPs question, post uvdos node.js but the error and title may bring others post uvdos node.js here who are getting this error.

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 wrong cmd .
npx post uvdos node.js create react-app assignment

cmd should be like
npx create-react-app post uvdos node.js my-project

mistake : I was missing «-» in between post uvdos node.js create and react in cmd

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

Angular was installed locally in this post uvdos node.js folder, which
already contained an post uvdos node.js Angular project.

In my case, I was using npm build.

It worked after changing to npm run post uvdos node.js build.