Bump the all-dependencies group with 3 updates

[dependabot]

Bumps the all-dependencies group with 3 updates: @typescript-eslint/eslint-plugin, @typescript-eslint/parser and esbuild.

Updates @typescript-eslint/eslint-plugin from 8.18.1 to 8.18.2

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v8.18.2

8.18.2 (2024-12-23)

🩹 Fixes

• eslint-plugin: [no-deprecated] not reporting usages of deprecated declared constants as object value (#10498)
• eslint-plugin: [prefer-reduce-type-parameter] don't report cases in which the fix results in a type error (#10494)
• eslint-plugin: [no-unnecessary-condition] don't flag values of an unconstrained or valid type parameter (#10473)
• eslint-plugin: [consistent-indexed-object-style] use a suggestion over an auto-fix if can't reliably determine that produced index signature is valid (#10490)
• eslint-plugin: [no-unsafe-type-assertion] fix for unsafe assertion to a constrained type parameter (#10461)
• eslint-plugin: [no-unnecessary-type-arguments] handle type/value context (#10503)
• eslint-plugin: [consistent-type-assertions] allow default assertionStyle option (#10512)
• eslint-plugin: [no-unnecessary-condition] handle noUncheckedIndexedAccess true (#10514)
• typescript-eslint: export types so that declarations can be named for dts files (#10513)

❤️ Thank You

• Brad Zacher @​bradzacher
• Luke Deen Taylor @​controversial
• Ronen Amiel
• Scott O'Hara
• YeonJuan @​yeonjuan
• Yukihiro Hasegawa @​y-hsgw

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

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

8.18.2 (2024-12-23)

🩹 Fixes

• eslint-plugin: [no-unnecessary-condition] handle noUncheckedIndexedAccess true (#10514)
• eslint-plugin: [consistent-type-assertions] allow default assertionStyle option (#10512)
• eslint-plugin: [no-unnecessary-type-arguments] handle type/value context (#10503)
• eslint-plugin: [no-unsafe-type-assertion] fix for unsafe assertion to a constrained type parameter (#10461)
• eslint-plugin: [consistent-indexed-object-style] use a suggestion over an auto-fix if can't reliably determine that produced index signature is valid (#10490)
• eslint-plugin: [no-unnecessary-condition] don't flag values of an unconstrained or valid type parameter (#10473)
• eslint-plugin: [prefer-reduce-type-parameter] don't report cases in which the fix results in a type error (#10494)
• eslint-plugin: [no-deprecated] not reporting usages of deprecated declared constants as object value (#10498)

❤️ Thank You

• Luke Deen Taylor @​controversial
• Ronen Amiel
• Scott O'Hara
• YeonJuan @​yeonjuan
• Yukihiro Hasegawa @​y-hsgw

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

Commits

• 157b781 chore(release): publish 8.18.2
• 83c3bbf fix(eslint-plugin): [no-unnecessary-condition] handle noUncheckedIndexedAcces...
• c6a387f fix(eslint-plugin): [consistent-type-assertions] allow default assertionStyle...
• 4747299 fix(eslint-plugin): [no-unnecessary-type-arguments] handle type/value context...
• 4c91ed5 fix(eslint-plugin): [no-unsafe-type-assertion] fix for unsafe assertion to a ...
• 91e7217 fix(eslint-plugin): [consistent-indexed-object-style] use a suggestion over a...
• dfd550d chore(deps): update dependency prettier to v3.4.2 (#10478)
• 8ca9cba fix(eslint-plugin): [no-unnecessary-condition] don't flag values of an uncons...
• ba39dde fix(eslint-plugin): [prefer-reduce-type-parameter] don't report cases in whic...
• 6c75493 fix(eslint-plugin): [no-deprecated] not reporting usages of deprecated declar...
• See full diff in compare view

Updates @typescript-eslint/parser from 8.18.1 to 8.18.2

Release notes

Sourced from @​typescript-eslint/parser's releases.

v8.18.2

8.18.2 (2024-12-23)

🩹 Fixes

• eslint-plugin: [no-deprecated] not reporting usages of deprecated declared constants as object value (#10498)
• eslint-plugin: [prefer-reduce-type-parameter] don't report cases in which the fix results in a type error (#10494)
• eslint-plugin: [no-unnecessary-condition] don't flag values of an unconstrained or valid type parameter (#10473)
• eslint-plugin: [consistent-indexed-object-style] use a suggestion over an auto-fix if can't reliably determine that produced index signature is valid (#10490)
• eslint-plugin: [no-unsafe-type-assertion] fix for unsafe assertion to a constrained type parameter (#10461)
• eslint-plugin: [no-unnecessary-type-arguments] handle type/value context (#10503)
• eslint-plugin: [consistent-type-assertions] allow default assertionStyle option (#10512)
• eslint-plugin: [no-unnecessary-condition] handle noUncheckedIndexedAccess true (#10514)
• typescript-eslint: export types so that declarations can be named for dts files (#10513)

❤️ Thank You

• Brad Zacher @​bradzacher
• Luke Deen Taylor @​controversial
• Ronen Amiel
• Scott O'Hara
• YeonJuan @​yeonjuan
• Yukihiro Hasegawa @​y-hsgw

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

Changelog

Sourced from @​typescript-eslint/parser's changelog.

8.18.2 (2024-12-23)

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

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

Commits

• 157b781 chore(release): publish 8.18.2
• See full diff in compare view

Updates esbuild from 0.24.0 to 0.24.2

Release notes

Sourced from esbuild's releases.

v0.24.2

• Fix regression with --define and import.meta (#4010, #4012, #4013)

  The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

  This fix was contributed by @​sapphi-red.

v0.24.1

• Allow es2024 as a target in tsconfig.json (#4004)

  TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2024"
    }
  }

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

  This fix was contributed by @​billyjanitsch.

• Allow automatic semicolon insertion after get/set

  This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

  class Foo {
    get
    *x() {}
    set
    *y() {}
  }

  The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

• Allow quoted property names in --define and --pure (#4008)

  The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

  // The following code now transforms to "return true;\n"
  console.log(esbuild.transformSync(
    `return process.env['SOME-TEST-VAR']`,
    { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },
  ))

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.24.2

• Fix regression with --define and import.meta (#4010, #4012, #4013)

  The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

  This fix was contributed by @​sapphi-red.

0.24.1

• Allow es2024 as a target in tsconfig.json (#4004)

  TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2024"
    }
  }

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

  This fix was contributed by @​billyjanitsch.

• Allow automatic semicolon insertion after get/set

  This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

  class Foo {
    get
    *x() {}
    set
    *y() {}
  }

  The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

• Allow quoted property names in --define and --pure (#4008)

  The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

  // The following code now transforms to "return true;\n"
  console.log(esbuild.transformSync(
    `return process.env['SOME-TEST-VAR']`,
    { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },

... (truncated)

Commits

• 745abd9 publish 0.24.2 to npm
• 79fd0b0 skip nulls in source map finalization (#4011)
• 4b9322f source map: avoid null entry for 0-length parts
• 199a0d3 close #4013: credit to @​sapphi-red for the fix
• 947f99f fix #4010, fix #4012: import.meta regression
• de9598f publish 0.24.1 to npm
• 15d56ca emit null source mappings for empty chunk content
• 8d98f6f fix #3985: entryPoint metadata for copy loader
• 0db1b82 fix #3998: avoid outbase in identifier names
• 7236472 close #3974: add support for netbsd on arm64
• Additional commits viewable 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

[dependabot]

Superseded by #1296.