Skip to content

chore(deps-dev): bump esbuild from 0.25.0 to 0.28.1 in /vscode-extension#147

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vscode-extension/esbuild-0.28.1
Closed

chore(deps-dev): bump esbuild from 0.25.0 to 0.28.1 in /vscode-extension#147
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vscode-extension/esbuild-0.28.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 14, 2026

Copy link
Copy Markdown
Contributor

Bumps esbuild from 0.25.0 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: 2025

This changelog documents all esbuild versions published in the year 2025 (versions 0.25.0 through 0.27.2).

0.27.2

  • Allow import path specifiers starting with #/ (#4361)

    Previously the specification for package.json disallowed import path specifiers starting with #/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping #/* to ./src/* (previously you had to use another character such as #_* instead, which was more confusing). There is some more context in nodejs/node#49182.

    This change was contributed by @​hybrist.

  • Automatically add the -webkit-mask prefix (#4357, #4358)

    This release automatically adds the -webkit- vendor prefix for the mask CSS shorthand property:

    /* Original code */
    main {
      mask: url(x.png) center/5rem no-repeat
    }
    /* Old output (with --target=chrome110) */
    main {
    mask: url(x.png) center/5rem no-repeat;
    }
    /* New output (with --target=chrome110) */
    main {
    -webkit-mask: url(x.png) center/5rem no-repeat;
    mask: url(x.png) center/5rem no-repeat;
    }

    This change was contributed by @​BPJEnnova.

  • Additional minification of switch statements (#4176, #4359)

    This release contains additional minification patterns for reducing switch statements. Here is an example:

    // Original code
    switch (x) {
      case 0:
        foo()
        break
      case 1:
      default:
        bar()
    }

... (truncated)

Commits
Maintainer changes

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


Dependabot compatibility score

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.

Bumps [esbuild](https://github.com/evanw/esbuild) from 0.25.0 to 0.28.1.
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2025.md)
- [Commits](evanw/esbuild@v0.25.0...v0.28.1)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.28.1
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 14, 2026
@dependabot
dependabot Bot requested a review from jung-thomas as a code owner June 14, 2026 01:04
@jung-thomas

Copy link
Copy Markdown
Contributor

Superseded by #160, which consolidates this update with the other pending dependency bumps into a single build- and test-validated PR. Closing in favor of that.

@dependabot @github

dependabot Bot commented on behalf of github Jul 11, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/vscode-extension/esbuild-0.28.1 branch July 11, 2026 18:19
jung-thomas added a commit that referenced this pull request Jul 11, 2026
* chore(deps): consolidate dependency updates across subprojects

Supersedes the 9 open Dependabot PRs (#146, #147, #148, #149, #151, #152,
#153, #156, #157) with one validated update. Direct-dep bumps plus lockfile
refreshes that absorb the transitive updates; each subproject's build and
test suite was run to confirm the majors are safe.

vscode-extension:
- @vscode/vsce 2.32 -> 3.9.2 (major), esbuild 0.25 -> 0.28.1 (#147, #149)
- transitives via lockfile: markdown-it 12->14, js-yaml 4.3, form-data 4.0.6,
  undici 7.28, tmp 0.2.7 (#146, #152, #153, #157)
- Verified: compile + esbuild bundle + `vsce package` succeed; the .vsix stays
  self-contained (webview assets present, zero native binaries).

app/vue:
- vite 6.3 -> 8.1.4 (two majors), @vitejs/plugin-vue 5.2 -> 6.0.7 (major),
  echarts 6.0 -> 6.1 (#148, #156)
- Verified: 46 vitest tests pass; `build` and `build:vscode` succeed and emit
  the webview assets consumed by the extension .vsix.

docs:
- dompurify 3.4.3 -> 3.4.11 via lockfile (transitive under mermaid) (#151)
- Verified: `docs:build` succeeds.

Root `test:ci` (550 passing) and `lint` remain green. Pre-existing app/vue
advisories (xlsx, dompurify-via-monaco) are untouched — out of scope and only
resolvable with breaking `audit fix --force`.

* chore(deps): upgrade to CAP 10 (@sap/cds 10) + cds-10-native cap-js drivers

Completes the CAP 10 migration on top of the consolidated dependency update.
The project's prior pre-work (compat flags already set to CAP 10 targets:
legacyLocking=false, ieee754compatible=true, compat_srv_getters=false,
compat_texts_entities=false) meant no runtime code changes were required.

- @sap/cds ^9.9.0 -> ^10.0.3
- @cap-js/hana 2.8 -> 3.0.1, @cap-js/sqlite 2.4 -> 3.0.2,
  @cap-js/postgres 2.3 -> 3.0.1, @cap-js/telemetry 1.6 -> 2.0.1
  (the 3.x/2.x majors declare `peer @sap/cds ^10`)
- Remove @sap/cds-hana: its cds-plugin throws "incompatible with @sap/cds
  version 9 and higher — use @cap-js/hana instead". Unused in source;
  @cap-js/hana already covers HANA connectivity.
- esbuild: mark generic-pool external — it's an OPTIONAL peer of
  @cap-js/db-service@3 whose require() is guarded behind the legacy pool
  path (CAP 10 uses the built-in pool), and it's not installed.

Audit: no CAP 10 breaking-change surface in source — no CAP req.params
(the one req.params is an Express route param), no ASSERT_MANDATORY matching,
no draft SAVE handlers, no @requires/req.user relying on skipped local checks.

Bonus: @cap-js/sqlite@3 makes better-sqlite3 an optional peer, so the native
binary is no longer installed at all — reinforcing the OS-portable .vsix.

Verified on CAP 10.0.3:
- root test:ci 550 passing; database+connection utils 50 passing; lint clean
- `cds compile` produces SQL; runtime SELECT via node:sqlite works,
  better-sqlite3 never loads
- extension bundles + packages: 352 webview assets, 0 native binaries

* chore(deps): refresh lockfiles for in-range patch/minor updates

`npm update` sweep across all projects to pull patch/minor bumps that sit
within existing semver ranges (no package.json changes needed):

- root: @cap-js-community/odata-v2-adapter 1.16, @wdio/* 9.29.1,
  chromedriver 150.0.3, eslint 10.6, terminal-kit 3.1.3, webdriverio,
  @types/node, hdb 2.29, sap-hdb-promisfied (lockfile only)
- docs: vue 3.5.39, @agentmarkup/vite 0.5.2 (56 transitive packages)
- app/vue, vscode-extension: already at wanted versions

Verified: root test:ci 550 passing, lint clean, docs:build and app/vue
vitest (46) green.

* chore(deps): upgrade TypeScript to 7 in vscode-extension and mcp-server

TypeScript 7.0 (the native compiler) builds both plain-tsc projects cleanly:
- vscode-extension: ^5.7 -> ^7.0.2 (compile, pretest, esbuild bundle all pass)
- mcp-server: ^6.0.2 -> ^7.0.2 (tsc build passes)

Regenerated mcp-server/build/ (committed output): only .d.ts and .js.map
files change — TS 7 emits single quotes in declarations. Zero runtime .js
changes; no behavior difference.

app/vue is intentionally NOT upgraded: vue-tsc@2 does
`require('typescript/lib/tsc')`, a subpath TS 7 removed from its exports map
(ERR_PACKAGE_PATH_NOT_EXPORTED). It needs vue-tsc@3 first — tracked in the
Group B follow-up issue. app/vue stays on TS 5.9 (within its ^5.7 range).

---------

Co-authored-by: Thomas Jung <12159356+jung-thomas@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant