build(deps-dev): bump the npm-development group across 1 directory with 3 updates

[dependabot]

Bumps the npm-development group with 3 updates in the / directory: @types/node, esbuild and vitest.

Updates @types/node from 20.11.30 to 20.12.11

Commits

• See full diff in compare view

Updates esbuild from 0.20.2 to 0.21.2

Release notes

Sourced from esbuild's releases.

v0.21.2

• Correct this in field and accessor decorators (#3761)

  This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

  const dec = () => function() { this.bar = true }
  class Foo { @dec static foo }
  console.log(Foo.bar) // Should be "true"

• Allow es2023 as a target environment (#3762)

  TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.

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() {

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.2

• Correct this in field and accessor decorators (#3761)

  This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

  const dec = () => function() { this.bar = true }
  class Foo { @dec static foo }
  console.log(Foo.bar) // Should be "true"

• Allow es2023 as a target environment (#3762)

  TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.

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
  }

... (truncated)

Commits

• b24180e publish 0.21.2 to npm
• f82e0ad fix #3761: this in field and accessor decorators
• 46ea596 fix #3762: add es2023 as an alias for es2022
• 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
• Additional commits viewable in compare view

Updates vitest from 1.4.0 to 1.6.0

Release notes

Sourced from vitest's releases.

v1.6.0

   🚀 Features

• Support standalone mode  -  by @​sheremet-va in vitest-dev/vitest#5565 (bdce0)
• Custom "snapshotEnvironment" option  -  by @​sheremet-va in vitest-dev/vitest#5449 (30f72)
• benchmark: Support comparing benchmark result  -  by @​hi-ogawa and @​sheremet-va in vitest-dev/vitest#5398 (f8d3d)
• browser: Allow injecting scripts  -  by @​sheremet-va in vitest-dev/vitest#5656 (21e58)
• reporter: Support includeConsoleOutput and addFileAttribute in junit  -  by @​hi-ogawa in vitest-dev/vitest#5659 (2f913)
• ui: Sort items by file name  -  by @​btea in vitest-dev/vitest#5652 (1f726)

   🐞 Bug Fixes

• Keep order of arguments for .each in custom task collectors  -  by @​sheremet-va in vitest-dev/vitest#5640 (7d57c)
• Call resolveId('vitest') after buildStart  -  by @​hi-ogawa in vitest-dev/vitest#5646 (f5faf)
• Hash the name of the file when caching  -  by @​sheremet-va in vitest-dev/vitest#5654 (c9e68)
• Don't panic on empty files in node_modules  -  by @​sheremet-va (40c29)
• Use toJSON for error serialization  -  by @​hi-ogawa in vitest-dev/vitest#5526 (19a21)
• coverage:
  • Exclude *.test-d.* by default  -  by @​MindfulPol in vitest-dev/vitest#5634 (bfe8a)
  • Apply vite-node's wrapper only to executed files  -  by @​AriPerkkio in vitest-dev/vitest#5642 (c9883)
• vm:
  • Support network imports  -  by @​sheremet-va in vitest-dev/vitest#5610 (103a6)

   🏎 Performance

• Improve performance of forks pool  -  by @​sheremet-va in vitest-dev/vitest#5592 (d8304)
• Unnecessary rpc call when coverage is disabled  -  by @​AriPerkkio in vitest-dev/vitest#5658 (c5712)

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

• Use package.json name for a workspace project if not provided  -  by @​sheremet-va in vitest-dev/vitest#5608 (48fba)
• Backport jest iterable equality within object  -  by @​sukovanej in vitest-dev/vitest#5621 (30e5d)
• browser: Support benchmark  -  by @​hi-ogawa in vitest-dev/vitest#5622 (becab)
• reporter: Use default error formatter for JUnit  -  by @​hi-ogawa in vitest-dev/vitest#5629 (20060)

    View changes on GitHub

v1.5.2

   🐞 Bug Fixes

• Check for null before storing in weakmap  -  by @​sheremet-va (ce368)

    View changes on GitHub

v1.5.1

   🚀 Features

... (truncated)

Commits

• 6b29f3d chore: release v1.6.0
• f8d3d22 feat(benchmark): support comparing benchmark result (#5398)
• 21e58bd feat(browser): allow injecting scripts (#5656)
• 30f728b feat: custom "snapshotEnvironment" option (#5449)
• 2f91322 feat(reporter): support includeConsoleOutput and addFileAttribute in juni...
• c571276 perf: unnecessary rpc call when coverage is disabled (#5658)
• bdce0a2 feat: support standalone mode (#5565)
• 40c299f fix: don't panic on empty files in node_modules
• c9e68ce fix: hash the name of the file when caching (#5654)
• f5faf42 fix: call resolveId('vitest') after buildStart (#5646)
• 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

• main
  • build(deps-dev): bump the npm-development group across 1 directory with 3 updates #23 👈

[dependabot]

Superseded by #24.