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.

v15.2.8

Compare Source

Patch Changes

• f0480f0 Thanks@​iiroj! - In the previous version the nativegit rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the--show-toplevel flag with--show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.jschild_process. The new flag returns a path relative to the working directory, avoiding the issue.

  The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

v15.2.7

Compare Source

Patch Changes

• #​1440a51be80 Thanks@​iiroj! - In the previous version the nativegit rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the--path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgradinggit to the latest version.

v15.2.6

Compare Source

Patch Changes

• #​1433119adb2 Thanks@​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

v15.2.5

Compare Source

Patch Changes

• #​142431a1f95 Thanks@​iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.

• #​142391abea0 Thanks@​iiroj! - Improve error logging when failing to read or parse a configuration file

• #​1424ee43f15 Thanks@​iiroj! - Upgrade micromatch@4.0.7

v15.2.4

Compare Source

Patch Changes

• 4f4537a Thanks@​iiroj! - Fix release issue with previous version; update dependencies

v15.2.2

Compare Source

Patch Changes

• #​1391fdcdad4 Thanks@​iiroj! -Lint-staged no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout.

v15.2.1

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.