Bump the all group across 1 directory with 5 updates

[dependabot]

Bumps the all group with 5 updates in the / directory:

Package	From	To
@types/node	22.10.2	22.10.3
commander	12.1.0	13.0.0
ignore	6.0.2	7.0.0
typescript-eslint	8.18.2	8.19.0
vite	6.0.5	6.0.6

Updates @types/node from 22.10.2 to 22.10.3

Commits

• See full diff in compare view

Updates commander from 12.1.0 to 13.0.0

Release notes

Sourced from commander's releases.

v13.0.0

Added

• support multiple calls to .parse() with default settings (#2299)
• add .saveStateBeforeParse() and .restoreStateBeforeParse() for use by subclasses (#2299)
• style routines like styleTitle() to add color to help using .configureHelp() or Help subclass (#2251)
• color related support in .configureOutput() for getOutHasColors(), getErrHasColors(), and stripColor() (#2251)
• Help property for minWidthToWrap (#2251)
• Help methods for displayWidth(), boxWrap(), preformatted() et al (#2251)

Changed

• Breaking: excess command-arguments cause an error by default, see migration tips (#2223)
• Breaking: throw during Option construction for unsupported option flags, like multiple characters after single - (#2270)
• Breaking: throw on multiple calls to .parse() if storeOptionsAsProperties: true (#2299)
• TypeScript: include implicit this in parameters for action handler callback (#2197)

Deleted

• Breaking: Help.wrap() refactored into formatItem() and boxWrap() (#2251)

Migration Tips

Excess command-arguments

It is now an error for the user to specify more command-arguments than are expected. (allowExcessArguments is now false by default.)

Old code:

program.option('-p, --port <number>', 'port number');
program.action((options) => {
  console.log(program.args);
});

Now shows an error:

$ node example.js a b c
error: too many arguments. Expected 0 arguments but got 3.

You can declare the expected arguments. The help will then be more accurate too. Note that declaring new arguments will change what is passed to the action handler.

program.option('-p, --port <number>', 'port number');
program.argument('[args...]', 'remote command and arguments'); // expecting zero or more arguments
program.action((args, options) => {
</tr></table> 

... (truncated)

Changelog

Sourced from commander's changelog.

[13.0.0] (2024-12-30)

Added

• support multiple calls to .parse() with default settings (#2299)
• add .saveStateBeforeParse() and .restoreStateBeforeParse() for use by subclasses (#2299)
• style routines like styleTitle() to add color to help using .configureHelp() or Help subclass (#2251)
• color related support in .configureOutput() for getOutHasColors(), getErrHasColors(), and stripColor() (#2251)
• Help property for minWidthToWrap (#2251)
• Help methods for displayWidth(), boxWrap(), preformatted() et al (#2251)

Changed

• Breaking: excess command-arguments cause an error by default, see migration tips (#2223)
• Breaking: throw during Option construction for unsupported option flags, like multiple characters after single - (#2270)
• Breaking: throw on multiple calls to .parse() if storeOptionsAsProperties: true (#2299)
• TypeScript: include implicit this in parameters for action handler callback (#2197)

Deleted

• Breaking: Help.wrap() refactored into formatItem() and boxWrap() (#2251)

Migration Tips

Excess command-arguments

It is now an error for the user to specify more command-arguments than are expected. (allowExcessArguments is now false by default.)

Old code:

program.option('-p, --port <number>', 'port number');
program.action((options) => {
  console.log(program.args);
});

Now shows an error:

$ node example.js a b c
error: too many arguments. Expected 0 arguments but got 3.

You can declare the expected arguments. The help will then be more accurate too. Note that declaring new arguments will change what is passed to the action handler.

program.option('-p, --port <number>', 'port number');
program.argument('[args...]', 'remote command and arguments'); // expecting zero or more arguments
</tr></table> 

... (truncated)

Commits

• d6bcb0b 13.0.0
• fa9e5ed Update release date
• fb2c46a Update CHANGELOG for 13.0.0 (#2301)
• 49423a2 Add save/restore state to allow multiple calls to parse (#2299)
• 497c11d Update dependencies (#2295)
• a8ef5cf Add informative message for missing executable on Windows (#2291)
• 02c603e Add clues about what help configuration is available to help with searches an...
• 37e86af Add links to CHANGELOG
• 53fc8a4 Prepare for 13.0.0-0 (#2292)
• d355b52 More Help documentation (#2282)
• Additional commits viewable in compare view

Updates ignore from 6.0.2 to 7.0.0

Release notes

Sourced from ignore's releases.

7.0.0

Minor feature

The primary feature introduced by 7.0.0 is the .checkIgnore() method, which is most equivalent to git check-ignore -v. And also it allows to pass {pattern, mark?} as the parameter of .add() so that we could imitate the mechanism of git check-ignore as:

ig.add({
  pattern: 'foo/*',
  mark: '60'
})
const {
ignored,
rule
} = checkIgnore('foo/')
if (ignored) {
console.log(.gitignore:${result}:${rule.mark}:${rule.pattern} foo/)
}
// .gitignore:60:foo/* foo/

Potential Incompatibilities

The only situation that 7.0.0 might bring incompatibility is to .add() a < 7.0.0 instance into a >= 7.0.0 instance, which might occur when the current workspace has multiple node-ignore versions installed, please be careful.

const {anotherIgnoreInstance} = require('./ignore-6.0-instance')
// A 7.0.0 instance
ignore().add(anotherIgnoreInstance)
// It will break your code

Otherwise, in most cases, if you never do something above or there is only one version of node-ignore installed in the current workspace, it is quite safe to upgrade to 7.0.0.

Commits

• See full diff in compare view

Updates typescript-eslint from 8.18.2 to 8.19.0

Release notes

Sourced from typescript-eslint's releases.

v8.19.0

8.19.0 (2024-12-30)

🚀 Features

• eslint-plugin: [strict-boolean-expressions] check array predicate functions' return statements (#10106)

🩹 Fixes

• eslint-plugin: add getConstraintInfo to handle generic constraints better (#10496)
• eslint-plugin: [array-type] autofix with conditional types needs parentheses (#10522)
• eslint-plugin: [consistent-indexed-object-style] don't report on indirect circular references (#10537)
• eslint-plugin: [member-ordering] ignore method overloading (#10536)

❤️ Thank You

• Karl Werner
• Kirk Waiblinger @​kirkwaiblinger
• Ronen Amiel
• YeonJuan @​yeonjuan

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from typescript-eslint's changelog.

8.19.0 (2024-12-30)

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

Commits

• e19f30f chore(release): publish 8.19.0
• See full diff in compare view

Updates vite from 6.0.5 to 6.0.6

Release notes

Sourced from vite's releases.

v6.0.6

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

6.0.6 (2024-12-26)

• fix: replace runner-side path normalization with fetchModule-side resolve (#18361) (9f10261), closes #18361
• fix(css): resolve style tags in HTML files correctly for lightningcss (#19001) (afff05c), closes #19001
• fix(css): show correct error when unknown placeholder is used for CSS modules pattern in lightningcs (9290d85), closes #19070
• fix(resolve): handle package.json with UTF-8 BOM (#19000) (902567a), closes #19000
• fix(ssrTransform): preserve line offset when transforming imports (#19004) (1aa434e), closes #19004
• chore: fix typo in comment (#19067) (eb06ec3), closes #19067
• chore: update comment about build.target (#19047) (0e9e81f), closes #19047
• revert: unpin esbuild version (#19043) (8bfe247), closes #19043
• test(ssr): test virtual module with query (#19044) (a1f4b46), closes #19044

Commits

• 5c2b4a0 release: v6.0.6
• 9290d85 fix(css): show correct error when unknown placeholder is used for CSS modules...
• afff05c fix(css): resolve style tags in HTML files correctly for lightningcss (#19001)
• eb06ec3 chore: fix typo in comment (#19067)
• 1aa434e fix(ssrTransform): preserve line offset when transforming imports (#19004)
• 902567a fix(resolve): handle package.json with UTF-8 BOM (#19000)
• 9f10261 fix: replace runner-side path normalization with fetchModule-side resolve (...
• 8bfe247 revert: unpin esbuild version (#19043)
• 0e9e81f chore: update comment about build.target (#19047)
• a1f4b46 test(ssr): test virtual module with query (#19044)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions