Bump esbuild and vite in /DevElevate/Client

[dependabot]

Bumps esbuild to 0.25.9 and updates ancestor dependency vite. These dependencies need to be updated together.

Updates esbuild from 0.18.20 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.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

• Fix TypeScript-specific class transform edge case (#3559)

  The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

  // Original code
  class Foo extends Bar {
    #private = 1;
    public: any;
    constructor() {
      super();
    }
  }
  // Old output (with esbuild v0.19.9)
  class Foo extends Bar {
  constructor() {
  super();
  this.#private = 1;
  }
  #private;
  }
  // Old output (with esbuild v0.19.10)
  class Foo extends Bar {
  constructor() {
  this.#private = 1;
  super();
  }
  #private;
  }
  // New output
  class Foo extends Bar {
  #private = 1;
  constructor() {
  super();
  }
  }

• Minifier: allow reording a primitive past a side-effect (#3568)

  The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (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

Updates vite from 4.5.14 to 7.1.3

Release notes

Sourced from vite's releases.

v7.1.3

Please refer to CHANGELOG.md for details.

v7.1.2

Please refer to CHANGELOG.md for details.

v7.1.1

Please refer to CHANGELOG.md for details.

create-vite@7.1.1

Please refer to CHANGELOG.md for details.

plugin-legacy@7.1.0

Please refer to CHANGELOG.md for details.

create-vite@7.1.0

Please refer to CHANGELOG.md for details.

v7.1.0

Please refer to CHANGELOG.md for details.

v7.1.0-beta.1

Please refer to CHANGELOG.md for details.

v7.1.0-beta.0

Please refer to CHANGELOG.md for details.

v7.0.6

Please refer to CHANGELOG.md for details.

v7.0.5

Please refer to CHANGELOG.md for details.

v7.0.4

Please refer to CHANGELOG.md for details.

v7.0.3

Please refer to CHANGELOG.md for details.

create-vite@7.0.3

Please refer to CHANGELOG.md for details.

v7.0.2

Please refer to CHANGELOG.md for details.

create-vite@7.0.2

Please refer to CHANGELOG.md for details.

v7.0.1

Please refer to CHANGELOG.md for details.

... (truncated)

Changelog

Sourced from vite's changelog.

7.1.3 (2025-08-19)

Features

• cli: add Node.js version warning for unsupported versions (#20638) (a1be1bf)
• generate code frame for parse errors thrown by terser (#20642) (a9ba017)
• support long lines in generateCodeFrame (#20640) (1559577)

Bug Fixes

• deps: update all non-major dependencies (#20634) (4851cab)
• optimizer: incorrect incompatible error (#20439) (446fe83)
• support multiline new URL(..., import.meta.url) expressions (#20644) (9ccf142)

Performance Improvements

• cli: dynamically import resolveConfig (#20646) (f691f57)

Miscellaneous Chores

• deps: update rolldown-related dependencies (#20633) (98b92e8)

Code Refactoring

• replace startsWith with strict equality (#20603) (42816de)
• use import in worker threads (#20641) (530687a)

Tests

• remove checkNodeVersion test (#20647) (731d3e6)

7.1.2 (2025-08-12)

Bug Fixes

• client: add [vite] prefixes to debug logs (#20595) (7cdef61)
• config: make debugger work with bundle loader (#20573) (c583927)
• deps: update all non-major dependencies (#20587) (20d4817)
• don't consider ids with npm: prefix as a built-in module (#20558) (ab33803)
• hmr: watch non-inlined assets referenced by CSS (#20581) (b7d494b)
• module-runner: prevent crash when sourceMappingURL pattern appears in string literals (#20554) (2770478)

Miscellaneous Chores

• deps: migrate to @jridgewell/remapping from @ampproject/remapping (#20577) (0a6048a)
• deps: update rolldown-related dependencies (#20586) (77632c5)

7.1.1 (2025-08-08)

Bug Fixes

• deps: update launch-editor-middleware (#20569) (826b394)

... (truncated)

Commits

• e090b7d release: v7.1.3
• 9ccf142 fix: support multiline new URL(..., import.meta.url) expressions (#20644)
• 731d3e6 test: remove checkNodeVersion test (#20647)
• a9ba017 feat: generate code frame for parse errors thrown by terser (#20642)
• 530687a refactor: use import in worker threads (#20641)
• a1be1bf feat(cli): add Node.js version warning for unsupported versions (#20638)
• 1559577 feat: support long lines in generateCodeFrame (#20640)
• f691f57 perf(cli): dynamically import resolveConfig (#20646)
• 446fe83 fix(optimizer): incorrect incompatible error (#20439)
• 42816de refactor: replace startsWith with strict equality (#20603)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vite since your current version.

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 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
dev-elevate	Ready	Preview	Comment	Aug 22, 2025 4:53pm

[github-actions]

🚀 Welcome to DevElevate PR!

Hi @dependabot[bot], thank you for your pull request! 🙌

📋 PR Details

• PR Bump esbuild and vite in /DevElevate/Client #381: Bump esbuild and vite in /DevElevate/Client
• Branch: dependabot/npm_and_yarn/DevElevate/Client/multi-ce50372528 → main
• Status: 🆕 New Pull Request

🔍 PR Analysis

Description: Bumps esbuild to 0.25.9 and updates ancestor dependency vite. These dependencies need to be updated together.

Updates esbuild from 0.18.20 to 0.25.9

Release notes

Sour...

✅ Checklist for Review

• Code follows project style guidelines
• Self-review completed
• Documentation updated (if applicable)
• Tests added/updated (if applicable)
• No breaking changes introduced
• All CI checks passing

🚀 Next Steps

1. Review: Our maintainers will review your PR within 24-48 hours
2. CI/CD: Automated checks will run to ensure code quality
3. Discussion: Feel free to respond to review comments
4. Merge: Once approved, your PR will be merged!

📚 Helpful Resources

• 📖 Contributing Guidelines
• 🔧 PR Template
• 💬 Join our Discord for discussions
• 🌟 GSSoC 2025 Program - We're an official participant!

🏷️ Auto-Labeling

This PR will be automatically labeled based on its content and files changed.

---

This is an automated message. For immediate assistance, please join our Discord server.

[github-actions]

🎉 Welcome to DevElevate, @dependabot[bot]!

🌟 First-Time Contributor Badge

🎊 Congratulations! You've just made your first contribution to DevElevate!

🎯 What This Means

• You're now part of our amazing open-source community
• Your contribution will help students and developers worldwide
• You're contributing to a GSSoC 2025 official project

🚀 Next Steps

1. Review Process: Our maintainers will review your PR
2. Feedback: You might receive suggestions for improvements
3. Merge: Once approved, your code will be merged!
4. Celebration: Your contribution will be visible on your GitHub profile

💡 Tips for Success

• Respond promptly to review comments
• Keep your PR focused and well-documented
• Don't hesitate to ask questions in the comments
• Join our Discord community for support

🏆 Recognition

• Your name will be added to our contributors list
• You'll receive a special mention in our release notes
• Consider applying for GSSoC 2025 if you're eligible!

---

Welcome to the DevElevate family! 🌟