Bump esbuild, vuepress and @vuepress/cli in /docs

[dependabot]

Bumps esbuild to 0.28.1 and updates ancestor dependencies esbuild, vuepress and @vuepress/cli. These dependencies need to be updated together.

Updates esbuild from 0.19.6 to 0.28.1

Release notes

Sourced from esbuild's releases.

v0.28.1

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#4461, #4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  // Old output
  new foo()bar();
  new (foo())?.bar();

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

• bb9db84 publish 0.28.1 to npm
• 9ff053e security: add integrity checks to the Deno API
• 0a9bf21 enforce non-negative size in gzip parser
• e2a1a71 security: forbid \\ in local dev server requests
• 83a2cbf fix #4482: don't inline using declarations
• 308ad74 fix #4471: renaming of nested var declarations
• f013f5f fix some typos
• aafd6e4 chore: fix some minor issues in comments (#4462)
• 15300c3 follow up: cjs evaluation fixes
• 1bda0c3 fix #4461, fix #4467: esm evaluation fixes
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for esbuild since your current version.

Updates vuepress from 2.0.0-rc.0 to 2.0.0-rc.30

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for vuepress since your current version.

Updates @vuepress/cli from 2.0.0-rc.0 to 2.0.0-rc.30

Release notes

Sourced from @​vuepress/cli's releases.

v2.0.0-rc.30

   🚀 Features

• core: Prepare user style separately  -  by @​Mister-Hope in vuepress/core#1700 (00801)
• markdown: Add aliasSupport option for assetsPlugin  -  by @​LincZero and @​Mister-Hope in vuepress/core#1646 and vuepress/core#1647 (d4f91)

    View changes on GitHub

v2.0.0-rc.29

   🚀 Features

• cli: Fix page file update racing problems and avoid middle state processing  -  by @​Mister-Hope in vuepress/core#1691 (da127)
• core: Add userStyle option to ensure highest css priority  -  by @​Mister-Hope and @​meteorlxy in vuepress/core#1110 and vuepress/core#1695 (071cc)

   🐞 Bug Fixes

• bundler-webpack: Update esbuild target option  -  by @​meteorlxy (925e6)

    View changes on GitHub

v2.0.0-rc.28

   🐞 Bug Fixes

• cli:
  • PagesWatcher should ignore files based on relative path  -  by @​Mister-Hope in vuepress/core#1689 (2e164)
  • Cleanup writeTemp on dev server restart  -  by @​Mister-Hope in vuepress/core#1693 (ab6ea)

    View changes on GitHub

v2.0.0-rc.27

   🚀 Features

• Upgrade vue-router to v5  -  by @​meteorlxy (d7773)
• Upgrade to vite 8 and migrate to rolldown  -  by @​meteorlxy (a59be)
• core:
  • Avoid race conditions when writing temp files  -  by @​pengzhanbo in vuepress/core#1674 (d89ac)
  • Optimize default value handling for options.locales  -  by @​pengzhanbo in vuepress/core#1676 (b0e36)

   🐞 Bug Fixes

• cli: Use a separate ignore matcher to ignore watched files  -  by @​Mister-Hope in vuepress/core#1681 (1ab52)
• core: Page creation should respect page options  -  by @​Mister-Hope in vuepress/core#1673 (b713e)

    View changes on GitHub

BREAKING CHANGES

• Page temp files have been removed. Now page components are loaded by bundler directly. If you rely on watching page temp files in dev mode, you can make use of the new onPageUpdated hook instead.
• markdown:
  • The markdown.assets.relativePathPrefix option has been removed, as it's redundant after removing page temp files.

... (truncated)

Changelog

Sourced from @​vuepress/cli's changelog.

2.0.0-rc.30 (2026-05-14)

Features

• core: prepare user style separately (#1700) (0080107)
• markdown: add aliasSupport option for assetsPlugin (close #1646) (#1647) (d4f9180)

2.0.0-rc.29 (2026-05-08)

Bug Fixes

• bundler-webpack: update esbuild target option (925e63a)

Features

• cli: fix page file update racing problems and avoid middle state processing (#1691) (da12787)
• core: add userStyle option to ensure highest css priority (close #1110) (#1695) (071cc21)

2.0.0-rc.28 (2026-04-01)

Bug Fixes

• cli: cleanup writeTemp on dev server restart (#1693) (ab6eada)
• cli: pagesWatcher should ignore files based on relative path (#1689) (2e164f5)

Code Refactoring

• core: update onPageUpdated hook params for delete event (#1692) (206e99e)

BREAKING CHANGES

• core: The onPageUpdated hook swaps the parameter order for delete type from ('delete', page, null) to ('delete', null, page).

2.0.0-rc.27 (2026-03-10)

Bug Fixes

• cli: use a separate ignore matcher to ignore watched files (#1681) (1ab52b6)
• core: page creation should respect page options (#1673) (b713ef4)

Features

... (truncated)

Commits

• dd5e0c4 build: publish v2.0.0-rc.30
• 987f8c1 ci: use pnpm ci to install dependencies (#1701)
• d4f9180 feat(markdown): add aliasSupport option for assetsPlugin (close #1646) (#1647)
• 0080107 feat(core): prepare user style separately (#1700)
• 281703e ci: add codeql workflow (#1699)
• 55307a3 build: publish v2.0.0-rc.29
• 8b96ee8 build: downgrade lint-staged for regression
• 071cc21 feat(core): add userStyle option to ensure highest css priority (close #1110)...
• 3140c3c ci: bump actions and drop node 20 (#1698)
• e334230 build: remove baseUrl from compilerOptions
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​vuepress/cli 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 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.