Sourced fromlint-staged's releases.

v16.0.0

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"$@":

  # my-script.sh#!/bin/bashecho"Staged files:$@"

  and

  {"*.js":"my-script.sh" }

  If you were using the shell option to avoid passing filenames to tasks, for examplebash -c 'tsc --noEmit', use the function syntax instead:

  exportdefault{'*.ts':()=>'tsc --noEmit'}

• #1546158d15c Thanks@​iiroj! - Validation for deprecated advanced configuration has been removed. The advanced configuration was removed inlint-staged version 9 and until now validation has failed if advanced configuration options were detected. Going forward the entire configuration will be treated with the same logic and if these advanced options are still present, they might be treated as valid globs for staged files instead.

• #1546158d15c Thanks@​iiroj! - The lowest supported Node.js version is20.18. Please upgrade your Node.js version.

Minor Changes

• #140127110ef Thanks@​RohitLuthra19! - Added support for directly running functions on staged files. To configure a function task, use an object with a title and the task itself:

  exportdefault{'*.js':{title:'My task',task:async(files)=>{console.log('Staged JS files:',files)},},}

... (truncated)

Sourced fromlint-staged's changelog.

16.0.0

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"$@":

  # my-script.sh#!/bin/bashecho"Staged files:$@"

  and

  {"*.js":"my-script.sh" }

  If you were using the shell option to avoid passing filenames to tasks, for examplebash -c 'tsc --noEmit', use the function syntax instead:

  exportdefault{'*.ts':()=>'tsc --noEmit'}

• #1546158d15c Thanks@​iiroj! - Validation for deprecated advanced configuration has been removed. The advanced configuration was removed inlint-staged version 9 and until now validation has failed if advanced configuration options were detected. Going forward the entire configuration will be treated with the same logic and if these advanced options are still present, they might be treated as valid globs for staged files instead.

• #1546158d15c Thanks@​iiroj! - The lowest supported Node.js version is20.18. Please upgrade your Node.js version.

Minor Changes

• #140127110ef Thanks@​RohitLuthra19! - Added support for directly running functions on staged files. To configure a function task, use an object with a title and the task itself:

  exportdefault{'*.js':{title:'My task',task:async(files)=>{console.log('Staged JS files:',files)},},}

... (truncated)

• dad5490 chore(changeset): release
• 1c19e82 build(deps): update dependencies and require Node.js 20.18
• 08cf8f5 docs: update README.md and bump nano-spawn as major change
• 276dcc8 refactor: simplify config validation
• d4b7cac test: update tests
• 0ee9ab8 fix: update TypeScript type definitions
• 12525b2 refactor: rename functions
• 541c353 refactor: separate "make cmd tasks" and "make function tasks"
• 27110ef feat: added support for custom configuration
• 52366f9 ci: update Node.js versions used in CI
• Additional commits viewable incompare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)