Skip to content

deps(vscode): bump esbuild from 0.24.2 to 0.28.0 in /editors/vscode in the vscode-minor-and-patch group across 1 directory - #4

Merged
trendvidia merged 1 commit into
mainfrom
dependabot/npm_and_yarn/editors/vscode/vscode-minor-and-patch-c39889ec24
May 7, 2026
Merged

deps(vscode): bump esbuild from 0.24.2 to 0.28.0 in /editors/vscode in the vscode-minor-and-patch group across 1 directory#4
trendvidia merged 1 commit into
mainfrom
dependabot/npm_and_yarn/editors/vscode/vscode-minor-and-patch-c39889ec24

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 7, 2026

Copy link
Copy Markdown
Contributor

Bumps the vscode-minor-and-patch group with 1 update in the /editors/vscode directory: esbuild.

Updates esbuild from 0.24.2 to 0.28.0

Release notes

Sourced from esbuild's releases.

v0.28.0

  • Add support for with { type: 'text' } imports (#4435)

    The import text proposal has reached stage 3 in the TC39 process, which means that it's recommended for implementation. It has also already been implemented by Deno and Bun. So with this release, esbuild also adds support for it. This behaves exactly the same as esbuild's existing text loader. Here's an example:

    import string from './example.txt' with { type: 'text' }
    console.log(string)
  • Add integrity checks to fallback download path (#4343)

    Installing esbuild via npm is somewhat complicated with several different edge cases (see esbuild's documentation for details). If the regular installation of esbuild's platform-specific package fails, esbuild's install script attempts to download the platform-specific package itself (first with the npm command, and then with a HTTP request to registry.npmjs.org as a last resort).

    This last resort path previously didn't have any integrity checks. With this release, esbuild will now verify that the hash of the downloaded binary matches the expected hash for the current release. This means the hashes for all of esbuild's platform-specific binary packages will now be embedded in the top-level esbuild package. Hopefully this should work without any problems. But just in case, this change is being done as a breaking change release.

  • Update the Go compiler from 1.25.7 to 1.26.1

    This upgrade should not affect anything. However, there have been some significant internal changes to the Go compiler, so esbuild could potentially behave differently in certain edge cases:

    • It now uses the new garbage collector that comes with Go 1.26.
    • The Go compiler is now more aggressive with allocating memory on the stack.
    • The executable format that the Go linker uses has undergone several changes.
    • The WebAssembly build now unconditionally makes use of the sign extension and non-trapping floating-point to integer conversion instructions.

    You can read the Go 1.26 release notes for more information.

v0.27.7

  • Fix lowering of define semantics for TypeScript parameter properties (#4421)

    The previous release incorrectly generated class fields for TypeScript parameter properties even when the configured target environment does not support class fields. With this release, the generated class fields will now be correctly lowered in this case:

    // Original code
    class Foo {
      constructor(public x = 1) {}
      y = 2
    }
    // Old output (with --loader=ts --target=es2021)
    class Foo {
    constructor(x = 1) {
    this.x = x;
    __publicField(this, "y", 2);
    }
    x;
    }
    // New output (with --loader=ts --target=es2021)
    class Foo {

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

Commits
  • 6a794df publish 0.28.0 to npm
  • 64ee0ea fix #4435: support with { type: text } imports
  • ef65aee fix sort order in snapshots_packagejson.txt
  • 1a26a8e try to fix test-old-ts, also shuffle CI tasks
  • 556ce6c use '' instead of null to omit build hashes
  • 8e675a8 ci: allow missing binary hashes for tests
  • 7067763 Reapply "update go 1.25.7 => 1.26.1"
  • 39473a9 fix #4343: integrity check for binary download
  • 2025c9f publish 0.27.7 to npm
  • c6b586e fix typo in Makefile for @esbuild/win32-x64
  • 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.


@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 7, 2026
Bumps the vscode-minor-and-patch group with 1 update in the /editors/vscode directory: [esbuild](https://github.com/evanw/esbuild).


Updates `esbuild` from 0.24.2 to 0.28.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md)
- [Commits](evanw/esbuild@v0.24.2...v0.28.0)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.28.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: vscode-minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title deps(vscode): bump esbuild from 0.24.2 to 0.28.0 in /editors/vscode in the vscode-minor-and-patch group deps(vscode): bump esbuild from 0.24.2 to 0.28.0 in /editors/vscode in the vscode-minor-and-patch group across 1 directory May 7, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/editors/vscode/vscode-minor-and-patch-c39889ec24 branch from 220fac1 to f63ecd1 Compare May 7, 2026 03:54
@trendvidia
trendvidia merged commit 5a5a152 into main May 7, 2026
4 checks passed
@trendvidia
trendvidia deleted the dependabot/npm_and_yarn/editors/vscode/vscode-minor-and-patch-c39889ec24 branch May 7, 2026 08:51
trendvidia added a commit that referenced this pull request May 14, 2026
Closes the README's schema-resolution-chain item #4: pxq now accepts
the same protoregistry coordinate triple the main `protowire` CLI
uses, fetches the named schema bundle from the gRPC server, and
hydrates every reachable message into the descriptor registry
alongside in-doc @proto, -p files, and the bundled canonical schemas.

Flags (mirroring cmd/protowire):
  -s, --server      protoregistry gRPC address (env: PROTOREGISTRY_SERVER)
  -n, --namespace   namespace within the registry (env: PROTOREGISTRY_NAMESPACE)
      --schema      schema id within the namespace

Implementation:

* New file registry.go: registryRef struct + fetchRegistry helper.
  registryRef carries the triple, exposes validated() for the
  partial-input error path (e.g. -s without -n) and active() for the
  gating decision. fetchRegistry uses grpc.NewClient + insecure
  credentials + a 10s timeout, exactly the cmd/protowire shape.
* schema.go: loadSchema gains the registryRef param; merges the
  fetched FileDescriptorSet using the shared registerFileDescriptorSet
  helper that descriptor-form in-doc @proto already used. One code
  path, two callers, single test surface.

Validation:
* 74 Go tests (67 from prior + 7 new). Tests cover:
    - validated() across the {empty, complete, server-only,
      namespace-missing, schema-missing} matrix
    - active() gating
    - registerFileDescriptorSet merge correctness
    - end-to-end fetchRegistry against an in-process gRPC server on
      a loopback port (no bufconn or dial overrides — the production
      grpc.NewClient call path is exercised unmodified)
    - loadSchema + registry merging the bundle into the schema
      alongside bundled canonical types
    - server-unreachable surfaces a clean error mentioning protoregistry
    - validated() runs before any network call
* CLI smoke test against a refused-connection address shows the error
  surfaces with the namespace/schema reference for diagnostic clarity:
    pxq: protoregistry GetDescriptor ns/s: rpc error: code = Unavailable …

Follow-ups remaining: strict-mode AST validator, pxq infer-schema
subcommand.
trendvidia added a commit that referenced this pull request Jul 17, 2026
…README layout (#115)

- Umbrella #30#35 ticked: M1 shipped June + the spec-#91/#35
  catch-up landed 2026-07-17 (protocompile#66/#67/#69 closed, PRs
  #70#72 + follow-ups #77#80).
- #4 round-trip box ticked: annotations.proto verified against
  protocompile @ 03ef9d8 (GH #58 closed) — parses clean, all 9
  declarations lower into FileAnnotationDecls; fixtures 01–06, 09,
  10, 12 all compile with zero diagnostics.
- #5 boxes ticked; README repository-layout now lists
  proto/schema/v1/{annotations,descriptor,report}.proto,
  proto/schema/config/v1/config.proto, and the draft -01 artifacts —
  the missing README listing was the one genuinely unmet box.
trendvidia added a commit that referenced this pull request Jul 24, 2026
- Implementation boxes #40#43 ticked: protocheck v2.0.0 (2026-07-23)
  shipped the engine SPI (PR#22), function registration + init-time
  verification (PR#23), and validation execution — WithFailFast (PR#21),
  wire-aligned EnrichedViolation model (PR#24), carrier-rule dispatch
  with source-map enrichment (PR#26); catalog + i18n (PR#28, M6).
  v2.1.0 added per-element repeated/map dispatch (PR#35).
- #50#52 ticked: protolsp shipped RFC-001 extended-grammar parsing
  and semantic tokens (protolsp#218 Phases A/B, 2026-07-16), source-map
  navigation with descriptor fallback (protolsp#219 Phase C, #220), and
  annotation-aware diagnostics (#220; completion parity #228,
  runtime-violation overlay #231).
- #70 ticked: protowire-go v1.3.1 (2026-07-23) wires the Validator
  seam through the pxf/pb/sbe decoders (protowire-go#49/PR#59) with the
  protocheck-side adapter (protocheck PR#38); protovalidate adapter as
  nested module (PR#60), noted on #17.
- M0 spec boxes #4#7 ticked (landed via GH #54; annotations.proto
  round-trip verified per GH #58); #6 acceptance boxes ticked against
  the shipped STABILITY.md section.
- #19 annotated: §5.3 executable fixtures shipped (GH #135, PR #138);
  corpus expansion continues in GH #68.

Remaining implementation fronts: #60/#61 (protobuf-go codegen) and
#80 (OpenAPI, GH #93).
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