Bump esbuild and vitest

[dependabot]

Bumps esbuild and vitest. These dependencies needed to be updated together.
Updates esbuild from 0.20.0 to 0.25.2

Release notes

Sourced from esbuild's releases.

v0.25.2

• Support flags in regular expressions for the API (#4121)

  The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the filter option. Internally these are translated into Go regular expressions. However, this translation previously ignored the flags property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression /\.[jt]sx?$/i is turned into the Go regular expression `(?i)\.[jt]sx?$` internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the i flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.

• Fix node-specific annotations for string literal export names (#4100)

  When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as exports.NAME = ... or module.exports = { ... }. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file export let foo, bar from ESM to CommonJS, esbuild appends this to the end of the file:

  // Annotate the CommonJS export names for ESM import in node:
  0 && (module.exports = {
    bar,
    foo
  });

  However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:

  // Original code
  let foo
  export { foo as "foo!" }
  // Old output (with --format=cjs --platform=node)
  ...
  0 && (module.exports = {
  "foo!"
  });
  // New output (with --format=cjs --platform=node)
  ...
  0 && (module.exports = {
  "foo!": null
  });

• Basic support for index source maps (#3439, #4109)

  The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.

  This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.

  Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.

  This feature was contributed by @​clyfish.

v0.25.1

• Fix incorrect paths in inline source maps (#4070, #4075, #4105)

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2024

This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).

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:

... (truncated)

Commits

• 4475787 publish 0.25.2 to npm
• 8f56771 fix #4121: map js regexp flags to go regexp flags
• 36b458d follow-up to #4109
• 8b8437c feat: support index source map (#4109)
• 75286c1 unit test for absolute windows paths in source map
• bcc77fb fix #4100: invalid identifiers in node annotation
• 37cb6a2 fix a warning from npm publish
• 6bfc1c1 publish 0.25.1 to npm
• f9b3952 fix #4078: prepend namespaces to source map paths
• ccf3dd7 add "contributed by" in changelog
• Additional commits viewable in compare view

Updates vitest from 1.2.2 to 3.1.1

Release notes

Sourced from vitest's releases.

v3.1.1

   🐞 Bug Fixes

• reporter:
  • Report tests in correct order  -  by @​sheremet-va in vitest-dev/vitest#7752 (b166e)
  • Print test only once in the verbose mode  -  by @​sheremet-va in vitest-dev/vitest#7738 (69ca4)

    View changes on GitHub

v3.1.0

🚀 Features

• Introduce %$ option to add number of the test to its title - by @​kemuridama in vitest-dev/vitest#7412 (df347)
• Add diff.maxDepth option and set non-Infinity value as a default to reduce crash - by @​hi-ogawa in vitest-dev/vitest#7481 (eacab)
• Allow array element for test.each/for title formatting - by @​hi-ogawa in vitest-dev/vitest#7522 (ea3d6)
• Add "configureVitest" plugin hook - by @​sheremet-va and @​AriPerkkio in vitest-dev/vitest#7349 (20a5d)
• Support --configLoader CLI option - by @​Carnageous and @​hi-ogawa in vitest-dev/vitest#7574 (2a852)
• Added vitest-browser-lit to vitest init browser and docs - by @​EskiMojo14 and @​hi-ogawa in vitest-dev/vitest#7705 (5659a)
• Use providers request interception for module mocking - by @​sheremet-va in vitest-dev/vitest#7576 (7883a)
• browser:
  • Introduce and, or and filter locators - by @​sheremet-va and @​AriPerkkio in vitest-dev/vitest#7463 (63949)
• reporter:
  • Always render test time - by @​AriPerkkio and @​spamshaker in vitest-dev/vitest#7529 (5eba6)
  • --silent=passed-only to log failed tasks only - by @​AriPerkkio in vitest-dev/vitest#7530 (f9e1c)
• runner:
  • Add test.scoped to override test.extend fixtures per-suite - by @​sheremet-va in vitest-dev/vitest#7233 (e5851)
• vitest:
  • Allow conditional context.skip(boolean) - by @​sheremet-va and @​AriPerkkio in vitest-dev/vitest#7659 (6adec)
  • Support rolldown-vite in NormalizeUrlPlugin - by @​sapphi-red and @​sheremet-va in vitest-dev/vitest#7739 (1ef31)

🐞 Bug Fixes

• Update test stats regularly - by @​hi-ogawa in vitest-dev/vitest#7700 (b7953)
• Fix vm tests flakiness - by @​sheremet-va in vitest-dev/vitest#7741 (2702c)
• Set diff.expand: false as default - by @​hi-ogawa in vitest-dev/vitest#7697 (f3420)
• browser:
  • Correctly calculate timeout in hooks when actions are performed - by @​sheremet-va in vitest-dev/vitest#7747 (a5505)
• deps:
  • Update all non-major dependencies - by @​hi-ogawa in vitest-dev/vitest#7600 (7fc5a)
• reporter:
  • --hideSkippedTests should hide suites too - by @​AriPerkkio in vitest-dev/vitest#7695 (ba9b5)
  • Report tests in correct order - by @​sheremet-va in vitest-dev/vitest#7752 (b166e)
  • Print test only once in the verbose mode - by @​sheremet-va in vitest-dev/vitest#7738 (69ca4)
• snapshot:
  • Fix indent normalization - by @​hi-ogawa in vitest-dev/vitest#7400 (82997)
  • This change can cause small amount of very old snapshots to be updated, but there will be no functional change to how they work.

🏎 Performance

• browser: Fork jest-dom instead of bundling it - by @​sheremet-va in vitest-dev/vitest#7605 (12762)

... (truncated)

Commits

• a9d36c7 chore: release v3.1.1
• 69ca425 fix(reporter): print test only once in the verbose mode (#7738)
• b166efa fix(reporter): report tests in correct order (#7752)
• b8eda4b chore: release v3.1.0
• 938da77 fix (ui): rerun individually tests with special chars in name (#7707)
• 7883acd feat: use providers request interception for module mocking (#7576)
• a7ecd0f refactor: remove direct imports from rollup (#7751)
• 5659a0e feat: Added vitest-browser-lit to vitest init browser and docs (#7705)
• 2702cf4 fix: fix vm tests flakiness (#7741)
• 12762ea perf(browser): fork jest-dom instead of bundling it (#7605)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by vitestbot, a new releaser for vitest since your current version.

You can trigger a rebase of this PR 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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.