chore(deps): bump the npm group across 1 directory with 3 updates

[dependabot]

Bumps the npm group with 3 updates in the / directory: esbuild, semver and eslint.

Updates esbuild from 0.20.2 to 0.21.1

Release notes

Sourced from esbuild's releases.

v0.21.1

• Fix a regression with --keep-names (#3756)

  The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

  // Original code
  x = { get y() {} }
  // Output from version 0.21.0 (with --keep-names)
  x = { get y: /* @PURE */ __name(function() {
  }, "y") };
  // Output from this version (with --keep-names)
  x = { get y() {
  } };

v0.21.0

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

• Implement the JavaScript decorators proposal (#104)

  With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:

  const log = (fn, context) => function() {
    console.log(`before ${context.name}`)
    const it = fn.apply(this, arguments)
    console.log(`after ${context.name}`)
    return it
  }
  class Foo {
  @​log static foo() {
  console.log('in foo')
  }
  }
  // Logs "before foo", "in foo", "after foo"
  Foo.foo()

  Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.

  Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.

  ⚠️ WARNING ⚠️

  This proposal has been in the works for a very long time (work began around 10 years ago in 2014) and it is finally getting close to becoming part of the JavaScript language. However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorators may need to be updated as the feature continues to evolve. The decorators proposal is pretty close to its final form but it can and likely will undergo some small behavioral adjustments before it ends up becoming a part of the standard. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.1

• Fix a regression with --keep-names (#3756)

  The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

  // Original code
  x = { get y() {} }
  // Output from version 0.21.0 (with --keep-names)
  x = { get y: /* @PURE */ __name(function() {
  }, "y") };
  // Output from this version (with --keep-names)
  x = { get y() {
  } };

0.21.0

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

• Implement the JavaScript decorators proposal (#104)

  With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:

  const log = (fn, context) => function() {
    console.log(`before ${context.name}`)
    const it = fn.apply(this, arguments)
    console.log(`after ${context.name}`)
    return it
  }
  class Foo {
  @​log static foo() {
  console.log('in foo')
  }
  }
  // Logs "before foo", "in foo", "after foo"
  Foo.foo()

  Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.

  Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.

  ⚠️ WARNING ⚠️

... (truncated)

Commits

• e876394 publish 0.21.1 to npm
• 4abc387 adjust decorator source map locations
• e7a9256 fix #3756: regression with --keep-names
• 33cbbea run make update-compat-table
• c6da2c3 publish 0.21.0 to npm
• 4bc834c initial implementation of the decorators proposal (#3754)
• 07cdbe0 some small adjustments to runtime library code
• 71b3d9f split off lowerPrivateMethod from lowerMethod
• 0861625 printer: preserve single-line status of block body
• f426153 runtime: make some helper functions more compact
• Additional commits viewable in compare view

Updates semver from 7.6.0 to 7.6.1

Release notes

Sourced from semver's releases.

v7.6.1

7.6.1 (2024-05-04)

Bug Fixes

• c570a34 #704 linting: no-unused-vars (@​wraithgar)
• ad8ff11 #704 use internal cache implementation (@​mbtools)
• ac9b357 #682 typo in compareBuild debug message (#682) (@​mbtools)

Dependencies

• 988a8de #709 uninstall lru-cache (#709)
• 3fabe4d #704 remove lru-cache

Chores

• dd09b60 #705 bump @​npmcli/template-oss to 4.22.0 (@​lukekarrys)
• ec49cdc #701 chore: chore: postinstall for dependabot template-oss PR (@​lukekarrys)
• b236c3d #696 add benchmarks (#696) (@​H4ad)
• 692451b #688 various improvements to README (#688) (@​mbtools)
• 5feeb7f #705 postinstall for dependabot template-oss PR (@​lukekarrys)
• 074156f #701 bump @​npmcli/template-oss from 4.21.3 to 4.21.4 (@​dependabot[bot])

Changelog

Sourced from semver's changelog.

7.6.1 (2024-05-04)

Bug Fixes

• c570a34 #704 linting: no-unused-vars (@​wraithgar)
• ad8ff11 #704 use internal cache implementation (@​mbtools)
• ac9b357 #682 typo in compareBuild debug message (#682) (@​mbtools)

Dependencies

• 988a8de #709 uninstall lru-cache (#709)
• 3fabe4d #704 remove lru-cache

Chores

• dd09b60 #705 bump @​npmcli/template-oss to 4.22.0 (@​lukekarrys)
• ec49cdc #701 chore: chore: postinstall for dependabot template-oss PR (@​lukekarrys)
• b236c3d #696 add benchmarks (#696) (@​H4ad)
• 692451b #688 various improvements to README (#688) (@​mbtools)
• 5feeb7f #705 postinstall for dependabot template-oss PR (@​lukekarrys)
• 074156f #701 bump @​npmcli/template-oss from 4.21.3 to 4.21.4 (@​dependabot[bot])

Commits

• d777418 chore: release 7.6.1 (#706)
• 988a8de deps: uninstall lru-cache (#709)
• 5feeb7f chore: postinstall for dependabot template-oss PR
• dd09b60 chore: bump @​npmcli/template-oss to 4.22.0
• c570a34 fix(linting): no-unused-vars
• ad8ff11 fix: use internal cache implementation
• 3fabe4d deps: remove lru-cache
• ec49cdc chore: chore: chore: postinstall for dependabot template-oss PR
• 074156f chore: bump @​npmcli/template-oss from 4.21.3 to 4.21.4
• b236c3d chore: add benchmarks (#696)
• Additional commits viewable in compare view

Updates eslint from 9.1.1 to 9.2.0

Release notes

Sourced from eslint's releases.

v9.2.0

Features

• 8485d76 feat: no-case-declarations add suggestions (#18388) (Josh Goldberg ✨)
• a498f35 feat: update Unicode letter detection in capitalized-comments rule (#18375) (Francesco Trotta)

Bug Fixes

• eeec413 fix: do not throw when defining a global named defineSetter (#18364) (唯然)

Documentation

• 0f5df50 docs: Update README (GitHub Actions Bot)
• 1579ce0 docs: update wording regarding indirect eval (#18394) (Kirk Waiblinger)
• f12a02c docs: update to eslint v9 in custom-rule-tutorial (#18383) (唯然)

Chores

• b346605 chore: upgrade @​eslint/js@​9.2.0 (#18413) (Milos Djermanovic)
• c4c18e0 chore: package.json update for @​eslint/js release (Jenkins)
• 284722c chore: package.json update for eslint-config-eslint release (Jenkins)
• 347d44f chore: remove eslintrc export from eslint-config-eslint (#18400) (Milos Djermanovic)
• f316e20 ci: run tests in Node.js 22 (#18393) (Francesco Trotta)

Changelog

Sourced from eslint's changelog.

v9.2.0 - May 3, 2024

• b346605 chore: upgrade @​eslint/js@​9.2.0 (#18413) (Milos Djermanovic)
• c4c18e0 chore: package.json update for @​eslint/js release (Jenkins)
• 284722c chore: package.json update for eslint-config-eslint release (Jenkins)
• 0f5df50 docs: Update README (GitHub Actions Bot)
• 347d44f chore: remove eslintrc export from eslint-config-eslint (#18400) (Milos Djermanovic)
• 8485d76 feat: no-case-declarations add suggestions (#18388) (Josh Goldberg ✨)
• a498f35 feat: update Unicode letter detection in capitalized-comments rule (#18375) (Francesco Trotta)
• 1579ce0 docs: update wording regarding indirect eval (#18394) (Kirk Waiblinger)
• f316e20 ci: run tests in Node.js 22 (#18393) (Francesco Trotta)
• eeec413 fix: do not throw when defining a global named defineSetter (#18364) (唯然)
• f12a02c docs: update to eslint v9 in custom-rule-tutorial (#18383) (唯然)

Commits

• 271e7ab 9.2.0
• 989ac9d Build: changelog update for 9.2.0
• b346605 chore: upgrade @​eslint/js@​9.2.0 (#18413)
• c4c18e0 chore: package.json update for @​eslint/js release
• 284722c chore: package.json update for eslint-config-eslint release
• 0f5df50 docs: Update README
• 347d44f chore: remove eslintrc export from eslint-config-eslint (#18400)
• 8485d76 feat: no-case-declarations add suggestions (#18388)
• a498f35 feat: update Unicode letter detection in capitalized-comments rule (#18375)
• 1579ce0 docs: update wording regarding indirect eval (#18394)
• 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

[ayushmanchhabra]

@dependabot squash and merge