v16.2.6

Compare Source

Patch Changes

• #​169333d4502 Thanks@​Adrian-Baran-GY! - Fix problems with--continue-on-error option, where tasks might have still been killed (SIGINT) when one of them failed.

v16.2.5

Compare Source

Patch Changes

• #​16879e02d9d Thanks@​iiroj! - Fix unhandled promise rejection when spawning tasks (instead of the tasks themselves failing). Previously when a task failed to spawn,lint-staged also failed and the backup stash might not have been automatically restored.

v16.2.4

Compare Source

Patch Changes

• #​16820176038 Thanks@​iiroj! - Update dependencies, includingnano-spawn@2.0.0 with bug fixes.

• #​1671581a54e Thanks@​iiroj! - Speed up execution by only importing theyaml depedency if using YAML configuration files.

v16.2.3

Compare Source

Patch Changes

• #​166927cd541 Thanks@​iiroj! - When using--fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to makelint-staged fail.

v16.2.2

Compare Source

Patch Changes

• #​1667699f95d Thanks@​iiroj! - The backup stash will not be dropped when using--fail-on-changes and there are errors. When reverting to original state is disabled (via--no-revert or--fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

  Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

  % npx lint-staged --fail-on-changes✔ Backed up original statein git stash (c18d55a3)✔ Running tasksfor staged files...✖ Tasks modified files and --fail-on-changes was used!↓ Cleaning up temporary files...✖ lint-staged failed because`--fail-on-changes` was used.Any lost modifications can be restored from a git stash:> git stash list --format="%h %s"  c18d55a3 On main: lint-staged automatic backup> git apply --index c18d55a3

v16.2.1

Compare Source

Patch Changes

• #​16648277b3b Thanks@​iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions isreadonly string[] and can't be mutated. Thanks@​outslept!

  export default {---  "*": (files: string[]) => void console.log('staged files', files)+++  "*": (files: readonly string[]) => void console.log('staged files', files)}

• #​165470b9af3 Thanks@​iiroj! - This version has been published from GitHub Actions usingTrusted Publishing for npm packages.

• #​16594996817 Thanks@​iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there arepackage.json files in the working directory. This situation might happen when runninglint-staged for a single package in a monorepo.

• #​16547021f0a Thanks@​iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates tolint-staged. This was changed in16.2.0 after the vulnerability issues withchalk anddebug, which were also removed in the same version.

  Given the recent vulnerabilities in thenpm ecosystem, it's best to be very careful when updating dependencies.

v16.2.0

Compare Source

Minor Changes

• #​161599eb742 Thanks@​iiroj! - Added a new option--fail-on-changes to makelint-staged exit with code 1 when tasks modify any files, making theprecommit hook fail. This is similar to thegit diff --exit-code option. Using this flag also implies the--no-revert flag which means any changes made by tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.

• #​1611cd05fd3 Thanks@​rlorenzo! - Added a new option--continue-on-error so thatlint-staged will run all tasks to completion even if some of them fail. By default,lint-staded will exit early on the first failure.

• #​163782fcc07 Thanks@​iiroj! - Internallint-staged errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there's a syntax error in thelint-staged configuration file.

• #​1647a5ecc06 Thanks@​iiroj! - Removedebug as a dependency due to recent malware issue; read more atdebug-js/debug#1005. Because of this, theDEBUG environment variable is no longer supported — use the--debug to enable debugging

• #​16368db2717 Thanks@​iiroj! - Added a new option--hide-unstaged so thatlint-staged will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags--hide-unstaged --no-hide-partially-staged isn't meaningful and behaves the same as just--hide-unstaged.

  Thanks to@​ItsNickBarry for the idea and initial implementation in#​1552.

• #​16487900b3b Thanks@​iiroj! - Removelilconfig to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly intolint-staged and should work about the same.

Patch Changes

• #​16337f9e485 Thanks@​dependabot! - Bumpslistr2 from 9.0.3 to 9.0.4.

• #​162699d5a9b Thanks@​iiroj! - Due to recent phishing attacks, for examplechalk@5.6.1 was released with malware. To avoidlint-staged's users being at risk thedirect dependencies are pinned to exact versions, instead of allowing future patch versions with thecaret (^) range.

• #​1588035bbf2 Thanks@​outslept! - Increase performance by listing staged files and searching for configuration concurrently.

• #​1645deba3ad Thanks@​iiroj! - Removechalk as a dependency due to recent malware issue; read more atchalk/chalk#656.

  If you are having trouble with ANSI color codes when usinglint-staged, you can try setting eitherFORCE_COLOR=true orNO_COLOR=true env variables.

v16.1.6

Compare Source

Patch Changes

• #​1610e93578e Thanks@​iiroj! - Try to improve terminating of subprocess of tasks by usingSIGKILL, and only callingpidtree when the the main task process has a known pid.

v16.1.5

Compare Source

Patch Changes

• #​16084e3ce22 Thanks@​srsatt! - Detect the git repo's top-level directory correctly when in a worktree.

v16.1.4

Compare Source

Patch Changes

• #​160490b37b0 Thanks@​iiroj! - Add anothertypes field topackage.json to make even more sure NPM detects thatlint-staged includes built-in TypeScript type definitions.

v16.1.3

Compare Source

Patch Changes

• #​16027ea700b Thanks@​dword-design! - Add thetypes field topackage.json to make sure NPM detectslint-staged includes built-in TypeScript type definitions.

v16.1.2

Compare Source

Patch Changes

• #​1570a7c0c88 Thanks@​ItsNickBarry! - When using--diff-filter with theD option to include deleted staged files,lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error fromgit add likefatal: pathspec 'deleted-file' did not match any files.

• 38f942e Thanks@​iiroj! - Removed an extraneous log entry that printedshouldHidePArtiallyStagedFiles to console output.

v16.1.1

Compare Source

Patch Changes

• #​15653686977 Thanks@​iiroj! -Lint-staged now explicitly warns about potential data loss when using--no-stash.

• #​157102299a9 Thanks@​iiroj! - Function tasks (introduced in v16.0.0) only receive the staged files matching the configured glob, instead of all staged files.

• #​1563bc61c74 Thanks@​iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the--no-stash option. This happened because--no-stash implied--no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit bylint-staged; this is no longer the case.

  The previous (incorrect) behavior can still be achieved by using both options--no-stash --no-hide-partially-staged at the same time.

v16.1.0

Compare Source

Minor Changes

• #​1536e729daa Thanks@​iiroj! - A new flag--no-revert has been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default,lint-staged will clear all task modifications and revert to the original state.

• #​1550b27fa3f Thanks@​iiroj! -Lint-staged now ignores symlinks and leaves them out from the list of staged files.

Patch Changes

• #​1558c37dc38 Thanks@​iiroj! - The minimum required Node.js version is lowered to20.17 followingnano-spawn@1.0.2.

v16.0.0

Compare Source

Major Changes

• #​1546158d15c Thanks@​iiroj! - Processes are spawned usingnano-spawn instead ofexeca. If you are using Node.js scripts as tasks, you might need to explicitly run them withnode, especially when using Windows:

  {"*.js":"node my-js-linter.js"}

• #​1546158d15c Thanks@​iiroj! - The--shell flag has been removed andlint-staged no longer supports evaluating commands directly via a shell. To migrate existing commands, you can create a shell script and invoke it instead. Lint-staged will pass matched staged files as a list of arguments, accessible via"$@​":

v15.5.2

Compare Source

Patch Changes

• #​15445561321 Thanks@​YimingIsCOLD! - Correctly handle colon (:) characters in staged filenames.

v15.5.1

Compare Source

Patch Changes

• #​15335d53534 Thanks@​iiroj! - Improve listing of staged files so thatlint-staged doesn't crash when encountering an uninitialized submodule. This should result in less errors like:

  ✖ Failed to get staged files!

v15.5.0

Compare Source

Minor Changes

• #​1526630af5f Thanks@​iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.

Example with Prettier

By default Prettierprefers double quotes.

Previously

1. Stagefile.js with only double quotes" changed to'
2. Rungit commit -am "I don't like double quotes"
3. Lint-staged runsprettier --write file.js, converting all the' back to"
4. Because there are now no changes,lint-staged fails, cancels the commit, and resets back to the original state
5. Commit was not done, original state is restored and single quotes' are staged

Now

1. Stagefile.js with only double-quotes" changed to'
2. Rungit commit -am "I don't like double quotes"
3. Lint-staged runsprettier --write file.js, converting all the' back to"
4. Because there are now no changes,lint-staged fails and cancels the commit
5. Commit was not done, and there are no staged changes

v15.4.3

Compare Source

Patch Changes

• #​1512cbfed1d Thanks@​tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.

v15.4.2

Compare Source

Patch Changes

• #​15098827ebf Thanks@​iiroj! - Changelint-staged's dependencies to usecaret (^) ranges instead oftilde (~). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.

v15.4.1

Compare Source

Patch Changes

• #​15041c7a45e Thanks@​iiroj! - Default TypeScript config filenames match JS equivalents.

• #​15049cc18c9 Thanks@​iiroj! - Add missing conditional exports syntax for TypeScript types.

v15.4.0

Compare Source

Minor Changes

• #​1500a8ec1dd Thanks@​iiroj! -Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:

  /** * @​filename: lint-staged.config.js * @​type {import('lint-staged').Configuration} */exportdefault{'*':'prettier --write',}

  It's also possible to use the.ts file extension for the configuration if your Node.js version supports it. The--experimental-strip-types flag was introduced inNode.js v22.6.0 and unflagged inv23.6.0, enabling Node.js to execute TypeScript files without additional configuration.

  export NODE_OPTIONS="--experimental-strip-types"npx lint-staged --config lint-staged.config.ts

Patch Changes

• #​15019b79364 Thanks@​iiroj! - Handle possible failures when logging user shell for debug info.

v15.3.0

Compare Source

Minor Changes

• #​1495e69da9e Thanks@​iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.

• #​1493fa0fe98 Thanks@​iiroj! - Added more help messages around the automaticgit stash thatlint-staged creates as a backup (by default). The console output also displays the short githash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.

  For example:

  % npx lint-staged✔ Backed up original state in git stash (20addf8)✔ Running tasks for staged files...✔ Applying modifications from tasks...✔ Cleaning up temporary files...

  where the backup can be seen withgit show 20addf8, orgit stash list:

  % git stash liststash@{0}: lint-staged automatic backup (20addf8)

v15.2.11

Compare Source

Patch Changes

• #​1484bcfe309 Thanks@​wormsik! - Escape paths containing spaces when using the "shell" option.

• #​14877dd8caa Thanks@​iiroj! - Do not treat submodule root paths as "staged files". This causedlint-staged to fail to a Git error when only updating the revision of a submodule.

v15.2.10

Compare Source

Patch Changes

• #​1471e3f283b Thanks@​iiroj! - Update minor dependencies, includingmicromatch@~4.0.8.

v15.2.9

Compare Source

Patch Changes

• #​1463b69ce2d Thanks@​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warningMaxListenersExceededWarning: Possible EventEmitter memory leak detected.