chore(deps-dev): bump the npm_and_yarn group across 1 directory with 3 updates

[dependabot]

Bumps the npm_and_yarn group with 3 updates in the / directory: rollup, vite and esbuild.

Updates rollup from 4.41.1 to 4.50.1

Release notes

Sourced from rollup's releases.

v4.50.1

4.50.1

2025-09-07

Bug Fixes

• Resolve a situation where a destructuring default value was removed (#6090)

Pull Requests

• #6088: feat(www): shorter repl shareables (@​cyyynthia, @​lukastaegert)
• #6090: Call includeNode for self or children nodes in includeDestructuredIfNecessary (@​TrickyPi)
• #6091: fix(deps): update rust crate swc_compiler_base to v33 (@​renovate[bot])
• #6092: chore(deps): lock file maintenance minor/patch updates (@​renovate[bot])
• #6094: perf: replace startsWith with strict equality (@​btea)

v4.50.0

4.50.0

2025-08-31

Features

• Support openharmony-arm64 platform (#6081)

Bug Fixes

• Fix loading of extensionless imports in config files (#6084)

Pull Requests

• #6081: Add support for openharmony-arm64 platform (@​hqzing, @​lukastaegert)
• #6084: Return null to defer to the default resolution behavior (@​TrickyPi)

v4.49.0

4.49.0

2025-08-27

Features

• Allow config plugins to resolve imports first before deciding whether to treat them as external (#6038)

Pull Requests

• #6038: feat: Run external check in cli/run/loadConfigFile.ts as last in order to allow handling of e.g. workspace package imports in TS monorepos correctly (@​stazz, @​TrickyPi)
• #6082: Improve build pipeline performance (@​lukastaegert)

v4.48.1

... (truncated)

Changelog

Sourced from rollup's changelog.

4.50.1

2025-09-07

Bug Fixes

• Resolve a situation where a destructuring default value was removed (#6090)

Pull Requests

• #6088: feat(www): shorter repl shareables (@​cyyynthia, @​lukastaegert)
• #6090: Call includeNode for self or children nodes in includeDestructuredIfNecessary (@​TrickyPi)
• #6091: fix(deps): update rust crate swc_compiler_base to v33 (@​renovate[bot])
• #6092: chore(deps): lock file maintenance minor/patch updates (@​renovate[bot])
• #6094: perf: replace startsWith with strict equality (@​btea)

4.50.0

2025-08-31

Features

• Support openharmony-arm64 platform (#6081)

Bug Fixes

• Fix loading of extensionless imports in config files (#6084)

Pull Requests

• #6081: Add support for openharmony-arm64 platform (@​hqzing, @​lukastaegert)
• #6084: Return null to defer to the default resolution behavior (@​TrickyPi)

4.49.0

2025-08-27

Features

• Allow config plugins to resolve imports first before deciding whether to treat them as external (#6038)

Pull Requests

• #6038: feat: Run external check in cli/run/loadConfigFile.ts as last in order to allow handling of e.g. workspace package imports in TS monorepos correctly (@​stazz, @​TrickyPi)
• #6082: Improve build pipeline performance (@​lukastaegert)

4.48.1

2025-08-25

... (truncated)

Commits

• 79d5563 4.50.1
• 7fb50f9 Call includeNode for self or children nodes in includeDestructuredIfNecessary...
• 235dc74 perf: replace startsWith with strict equality (#6094)
• a2744ea feat(www): shorter repl shareables (#6088)
• 298609e chore(deps): lock file maintenance minor/patch updates (#6092)
• 3d9de27 fix(deps): update rust crate swc_compiler_base to v33 (#6091)
• 592e7d7 4.50.0
• 06df2d6 Split up changelog file
• 38a5c6d Add support for openharmony-arm64 platform (#6081)
• bd02778 Return null to defer to the default resolution behavior (#6084)
• Additional commits viewable in compare view

Updates vite from 6.3.5 to 6.3.6

Release notes

Sourced from vite's releases.

v6.3.6

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

6.3.6 (2025-09-08)

• fix: apply fs.strict check to HTML files (#20736) (0ab19ea), closes #20736
• fix: upgrade sirv to 3.0.2 (#20735) (e11d240), closes #20735
• test: detect ts support via process.features (#20544) (7d99229), closes #20544

Commits

• 3f337c5 release: v6.3.6
• e11d240 fix: upgrade sirv to 3.0.2 (#20735)
• 0ab19ea fix: apply fs.strict check to HTML files (#20736)
• 7d99229 test: detect ts support via process.features (#20544)
• See full diff in compare view

Updates esbuild from 0.25.5 to 0.25.9

Release notes

Sourced from esbuild's releases.

v0.25.9

• Better support building projects that use Yarn on Windows (#3131, #3663)

  With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

  1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
  2. Some developers put their projects on the D: drive
  3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
  4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
  5. I didn't have access to a Windows machine for testing this edge case

  Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.

• Preserve parentheses around function expressions (#4252)

  The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

  Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:

  // Original code
  const fn0 = () => 0
  const fn1 = (() => 1)
  console.log(fn0, function() { return fn1() }())
  // Old output
  const fn0 = () => 0;
  const fn1 = () => 1;
  console.log(fn0, function() {
  return fn1();
  }());
  // New output
  const fn0 = () => 0;
  const fn1 = (() => 1);
  console.log(fn0, (function() {
  return fn1();
  })());

  Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.

• Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

  This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

v0.25.8

• Fix another TypeScript parsing edge case (#4248)

  This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.25.9

• Better support building projects that use Yarn on Windows (#3131, #3663)

  With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

  1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
  2. Some developers put their projects on the D: drive
  3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
  4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
  5. I didn't have access to a Windows machine for testing this edge case

  Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.

• Preserve parentheses around function expressions (#4252)

  The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

  Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:

  // Original code
  const fn0 = () => 0
  const fn1 = (() => 1)
  console.log(fn0, function() { return fn1() }())
  // Old output
  const fn0 = () => 0;
  const fn1 = () => 1;
  console.log(fn0, function() {
  return fn1();
  }());
  // New output
  const fn0 = () => 0;
  const fn1 = (() => 1);
  console.log(fn0, (function() {
  return fn1();
  })());

  Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.

• Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

  This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

0.25.8

• Fix another TypeScript parsing edge case (#4248)

... (truncated)

Commits

• 195e05c publish 0.25.9 to npm
• 3dac33f fix #3131, fix #3663: yarnpnp + windows + D drive
• 0f2c5c8 mock fs now supports multiple volumes on windows
• 100a51e split out yarnpnp snapshot tests
• 13aace3 remove C: assumption from windows snapshot tests
• f1f413f fix #4252: preserve parentheses around functions
• 1bc8091 fix #4257, close #4258: go 1.23.10 => 1.23.12
• bc52135 move the go compiler version to go.version
• a0af5d1 makefile: use ESBUILD_VERSION consistently
• 8c71947 publish 0.25.8 to npm
• 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
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mergify]

Automatically approving dependabot

[gavmck]

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀