lint-staged command is not found #618

fayfang · 2019-12-04T01:16:26Z

when I use package.json below, the output is 'lint-staged command is not found'

{
  "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  ...
}

when I use the npm command like this, It work

{
  "scripts": {
    "lint": "lint-staged"
  },
  "husky": {
    "hooks": {
      "pre-commit": "npm run lint"
    }
  },
  ...
}

How can I fix it up?

OS: windows
terminal: git bash
git version: 2.17

$ HUSKY_DEBUG=1 git commit
PS D:\Users\fangyy001\Desktop\project\veb-third-web\cmbwp> git commit
husky > pre-commit (node v12.13.0)
'lint-staged' 不是内部或外部命令，也不是可运行的程序

Ryuno-Ki · 2019-12-06T08:50:36Z

Hi fayfang,

lint-staged is another package. Run npm install lint-staged --save-dev to install it.

fayfang · 2019-12-09T01:06:32Z

Hi fayfang,

lint-staged is another package. Run npm install lint-staged --save-dev to install it.

yeah, but I am confused that why the cmd in ./node_module/.bin can not be used when git commit. not only the lint-staged ,but also all the cmd in ./node_module/.bin can not be used.

Ryuno-Ki · 2019-12-18T06:16:33Z

Can you show the error message?
(In case you're using macOS or a GNU/Linux distribution, force an English message via LC_ALL=C ./node_modules/.bin/husky resp. with the git command).

typicode · 2020-01-07T02:41:01Z

It may be worth testing with Husky v4.

As the reason why npm run lint works but not calling lint-staged directly, I suspect it's because npm run modifies PATH to include node_modules/.bin. On the other side, when hook commands are run PATH isn't modified.

barretron · 2020-01-10T15:18:33Z

On the other side, when hook commands are run PATH isn't modified.

Is this an intentional change in behavior from v3? I'm running into the same issue.

Manubi · 2020-12-02T10:41:24Z

.husky/pre-commit: line 4: lint-staged: command not found
I get now this error message with husky v5.0.4 and lint-staged v10.5.1.

Update: Adding yarn lint-staged to the pre-commit husky file fixed it.

typicode · 2020-12-03T08:06:07Z

Update: Adding yarn lint-staged to the pre-commit husky file fixed it.

That's the right fix, for husky v5 and v4, locally installed commands need to be run via the package manager.
So yarn lint-staged or npx --no-install lint-staged will work.

Alternatively, this will work too:

// .husky/pre-commit (v5) or .huskyrc (v4)
npm run pre-commit

// package.json
{
  "scripts": {
    "pre-commit": "lint-staged"
  }
}

AbnerPS · 2021-02-13T23:10:31Z

If the husky hook is not being called, try to install version 4: npm install husky@4 --save-dev

Electron v12 introduced a breaking change, so we need to set contextIsolation to false for our app to continue to work. Also update husky to fix husky-run command not found, as seen in typicode/husky/issues/854, and lint-staged not found, in typicode/husky/issues/618 and prettier config change https://github.com/prettier/eslint-config-prettier/blob/main/CHANGELOG.md#version-800-2021-02-21

scoobster17 · 2021-09-07T15:35:17Z

To follow @typicode's message:

I suspect it's because npm run modifies PATH to include node_modules/.bin. On the other side, when hook commands are run PATH isn't modified.

If you change your .husky/pre-commit to include this path, it works with husky@latest:

#!/bin/sh
. "$(dirname "$0")/_/husky.sh"

node_modules/.bin/lint-staged

- Run linters against staged git files and don't let 💩 slip into your code base! Linting makes more sense when run before committing your code. By doing so you can ensure no errors go into the repository and enforce code style. But running a lint process on a whole project is slow, and linting results can be irrelevant. Ultimately you only want to lint files that will be committed. Steps: - Install the npm package `lint-staged` with the command: `npm install lint-staged --save-dev` - Add the configuration to the `.lintstagedrc` file. This will run `npm run lint` on the files that have been modified and are being prepared for upload. - Change the `npm run lint` to `npx lint-staged` on the `pre-commit` file. Husky instead of directly running `npm run lint` will run `lint-staged` so you don't have to check all the files in the repository at once. References: - https://www.youtube.com/watch?v=jNxDNoYEGVU - https://dev.to/truemark/run-eslint-on-git-commit-with-husky-and-lint-staged-in-reactjs-4oeb - typicode/husky#618 - https://www.npmjs.com/package/lint-staged#Configuration

michelmany · 2022-10-28T13:49:14Z

Adding npx lint-staged to the pre-commit husky file fixed it for me.

officialkevinbrian · 2023-01-07T09:08:37Z

Adding npx lint-staged to the pre-commit husky file fixed it for me.

Also this worked for me.

SercanSercan · 2023-01-11T14:34:07Z

If you are also desperately trying to fix ".husky/pre-commit: line 4: lint-staged: command not found", add "npx lint-staged" to your pre-commit file. Read more about the solution here: https://storksnestblog.wordpress.com/2023/01/11/fixing-husky-lint-staged-command-not-found-error/

SercanSercan · 2023-01-11T14:35:10Z

Adding npx lint-staged to the pre-commit husky file fixed it for me.

I should've read your comment earlier :D

…ook from Intellij commit GUI. Solution found here typicode/husky#618 (comment)

Steps: - Install the `lint-staged` package using the command: `npm install lint-staged -D` - Make a clean installation: 1. Delete the `node_modules` folder and the `package-lock.json` file. 2. Reinstall the packages with the command: `npm install --ignore-scripts` Reason: - Sometimes, when saving a file, errors are not corrected automatically. That is why I add the `lint-staged` package, to make sure there are no formatting errors before uploading the changes to the remote repository. References: - https://www.youtube.com/watch?v=jNxDNoYEGVU - https://dev.to/truemark/run-eslint-on-git-commit-with-husky-and-lint-staged-in-reactjs-4oeb - typicode/husky#618 - https://www.npmjs.com/package/lint-staged#Configuration

Description: - Run linters against staged git files and don't let 💩 slip into your code base! Linting makes more sense when run before committing your code. By doing so you can ensure no errors go into the repository and enforce code style. But running a lint process on a whole project is slow, and linting results can be irrelevant. Ultimately you only want to lint files that will be committed. Steps: - Run the following command to create the `.husky/pre-commit` file: `npx husky add .husky/pre-commit "npx lint-staged"` Husky instead of directly running `npm run lint` will run `lint-staged` so you don't have to check all the files in the repository at once. - Create the `.lintstagedrc` file and add the configuration to run the `npm run lint` command when any file changes. This will run `npm run lint` on files that have been modified and are being prepared for upload. - Create the `.huskyrc` file and add the configuration to use `lint-staged` when `husky` runs the `pre-commit` hook. With this setting the `lint` command is executed before committing changes. So the project files are always formatted with `prettier`, `stylelint` and `eslint`. References: - https://www.youtube.com/watch?v=jNxDNoYEGVU - https://dev.to/truemark/run-eslint-on-git-commit-with-husky-and-lint-staged-in-reactjs-4oeb - typicode/husky#618 - https://www.npmjs.com/package/lint-staged#Configuration

fox1t mentioned this issue Feb 7, 2020

lint-staged v10.0.7 doesnt trigger husky v4.2.1 (husky v4.0.0-beta.5 works) #667

Closed

barretron mentioned this issue Mar 3, 2020

Husky 4.x: Usage of SHELL environment variable can cause unexpected behavior #683

Closed

typicode closed this as completed Dec 3, 2020

alexandr-g mentioned this issue Feb 5, 2021

Upgrade husky to v5 facebook/create-react-app#10512

Open

alexleventer mentioned this issue Jan 19, 2022

Improve pre-commit hook OlympusDAO/olympus-frontend#1274

Merged

torkjels added a commit to brako-consulting/brako-no that referenced this issue Mar 14, 2023

Fix bug where lint-staged command was not found when running commit h…

2c8dae3

…ook from Intellij commit GUI. Solution found here typicode/husky#618 (comment)

981377660LMT mentioned this issue Jul 4, 2023

macos .husky/pre-commit: line 4: lint-staged: command not found 的问题 981377660LMT/ts#279

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

lint-staged command is not found #618

lint-staged command is not found #618

fayfang commented Dec 4, 2019

Ryuno-Ki commented Dec 6, 2019

fayfang commented Dec 9, 2019

Ryuno-Ki commented Dec 18, 2019

typicode commented Jan 7, 2020

barretron commented Jan 10, 2020

Manubi commented Dec 2, 2020 •

edited

Loading

typicode commented Dec 3, 2020

AbnerPS commented Feb 13, 2021

scoobster17 commented Sep 7, 2021

michelmany commented Oct 28, 2022

officialkevinbrian commented Jan 7, 2023

SercanSercan commented Jan 11, 2023

SercanSercan commented Jan 11, 2023

lint-staged command is not found #618

lint-staged command is not found #618

Comments

fayfang commented Dec 4, 2019

Ryuno-Ki commented Dec 6, 2019

fayfang commented Dec 9, 2019

Ryuno-Ki commented Dec 18, 2019

typicode commented Jan 7, 2020

barretron commented Jan 10, 2020

Manubi commented Dec 2, 2020 • edited Loading

typicode commented Dec 3, 2020

AbnerPS commented Feb 13, 2021

scoobster17 commented Sep 7, 2021

michelmany commented Oct 28, 2022

officialkevinbrian commented Jan 7, 2023

SercanSercan commented Jan 11, 2023

SercanSercan commented Jan 11, 2023

Manubi commented Dec 2, 2020 •

edited

Loading