Skip to content

Bump esbuild, @cloudflare/vitest-pool-workers, wrangler and vitest #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
May 15, 2025
Merged

Bump esbuild, @cloudflare/vitest-pool-workers, wrangler and vitest #12

merged 1 commit into from
May 15, 2025

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github May 15, 2025 •
edited
Loading

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

Bumps esbuild to 0.25.4 and updates ancestor dependencies esbuild, @cloudflare/vitest-pool-workers, wrangler and vitest. These dependencies need to be updated together.

Updates esbuild from 0.17.19 to 0.25.4

Release notes

Sourced from esbuild's releases.

v0.25.4

  • Add simple support for CORS to esbuild's development server (#4125)

    Starting with version 0.25.0, esbuild's development server is no longer configured to serve cross-origin requests. This was a deliberate change to prevent any website you visit from accessing your running esbuild development server. However, this change prevented (by design) certain use cases such as "debugging in production" by having your production website load code from localhost where the esbuild development server is running.

    To enable this use case, esbuild is adding a feature to allow Cross-Origin Resource Sharing (a.k.a. CORS) for simple requests. Specifically, passing your origin to the new cors option will now set the Access-Control-Allow-Origin response header when the request has a matching Origin header. Note that this currently only works for requests that don't send a preflight OPTIONS request, as esbuild's development server doesn't currently support OPTIONS requests.

    Some examples:

    • CLI:

      esbuild --servedir=. --cors-origin=https://example.com

    • JS:

      const ctx = await esbuild.context({})
await ctx.serve({
  servedir: '.',
  cors: {
    origin: 'https://example.com',
  },
})

    • Go:

      ctx, _ := api.Context(api.BuildOptions{})
ctx.Serve(api.ServeOptions{
  Servedir: ".",
  CORS: api.CORSOptions{
    Origin: []string{"https://example.com"},
  },
})

    The special origin * can be used to allow any origin to access esbuild's development server. Note that this means any website you visit will be able to read everything served by esbuild.

  • Pass through invalid URLs in source maps unmodified (#4169)

    This fixes a regression in version 0.25.0 where sources in source maps that form invalid URLs were not being passed through to the output. Version 0.25.0 changed the interpretation of sources from file paths to URLs, which means that URL parsing can now fail. Previously URLs that couldn't be parsed were replaced with the empty string. With this release, invalid URLs in sources should now be passed through unmodified.

  • Handle exports named __proto__ in ES modules (#4162, #4163)

    In JavaScript, the special property name __proto__ sets the prototype when used inside an object literal. Previously esbuild's ESM-to-CommonJS conversion didn't special-case the property name of exports named __proto__ so the exported getter accidentally became the prototype of the object literal. It's unclear what this affects, if anything, but it's better practice to avoid this by using a computed property name in this case.

    This fix was contributed by @​magic-akari.

... (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
  • 218d29e publish 0.25.4 to npm
  • e66cd0b dev server: simple support for CORS requests (#4171)
  • 8bf3368 js api: validate some options as arrays of strings
  • 1e7375a js api: simplify comma-separated array validation
  • 5f5964d release notes for #4163
  • adb5284 fix: handle __proto__ as a computed property in exports and add tests for s...
  • 0aa9f7b fix #4169: keep invalid source map URLs unmodified
  • 5959289 add additional guards for #4114 when using :is()
  • 677910b publish 0.25.3 to npm
  • a41040e fix #4110: support custom non-IP host values
  • Additional commits viewable in compare view

Updates @cloudflare/vitest-pool-workers from 0.5.33 to 0.8.29

Release notes

Sourced from @​cloudflare/vitest-pool-workers's releases.

@​cloudflare/vitest-pool-workers@​0.8.29

Patch Changes

@​cloudflare/vitest-pool-workers@​0.8.28

Patch Changes

@​cloudflare/vitest-pool-workers@​0.8.27

Patch Changes

@​cloudflare/vitest-pool-workers@​0.8.26

Patch Changes

@​cloudflare/vitest-pool-workers@​0.8.25

Patch Changes

@​cloudflare/vitest-pool-workers@​0.8.24

Patch Changes

@​cloudflare/vitest-pool-workers@​0.8.23

Patch Changes

@​cloudflare/vitest-pool-workers@​0.8.22

Patch Changes

... (truncated)

Changelog

Sourced from @​cloudflare/vitest-pool-workers's changelog.

0.8.29

Patch Changes

0.8.28

Patch Changes

0.8.27

Patch Changes

0.8.26

Patch Changes

0.8.25

Patch Changes

0.8.24

Patch Changes

0.8.23

Patch Changes

... (truncated)

Commits

Updates wrangler from 3.92.0 to 4.15.1

Release notes

Sourced from wrangler's releases.

[email protected]

Patch Changes

  • #9248 07f4010 Thanks @​vicb! - fix unenv version mismatch

  • #9219 ea71df3 Thanks @​vicb! - bump unenv to 2.0.0-rc.17

  • #9246 d033a7d Thanks @​edmundhung! - fix: strip CF-Connecting-IP header within fetch

    In v4.15.0, Miniflare began stripping the CF-Connecting-IP header via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches the fetch API to strip the header during local wrangler dev sessions as a temporary workaround until the underlying issue is resolved.

  • Updated dependencies [f61a08e, ea71df3, d033a7d]:

[email protected]

Minor Changes

  • #8794 02f0699 Thanks @​eastlondoner! - This adds support for more accurate types for service bindings when running wrangler types. Previously, running wrangler types with a config including a service binding would generate an Env type like this:

    interface Env {
	SERVICE_BINDING: Fetcher;
}

    This type was "correct", but didn't capture the possibility of using JSRPC to communicate with the service binding. Now, running wrangler types -c wrangler.json -c ../service/wrangler.json (the first config representing the current Worker, and any additional configs representing service bound Workers) will generate an Env type like this:

    interface Env {
	SERVICE_BINDING: Service<import("../service/src/index").Entrypoint>;
}

  • #8716 63a6504 Thanks @​ItsWendell! - add --metafile flag to generate esbuild metadata file during build

  • #9122 f17ee08 Thanks @​avenceslau! - Unhide wrangler workflows delete command

Patch Changes

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.15.1

Patch Changes

  • #9248 07f4010 Thanks @​vicb! - fix unenv version mismatch

  • #9219 ea71df3 Thanks @​vicb! - bump unenv to 2.0.0-rc.17

  • #9246 d033a7d Thanks @​edmundhung! - fix: strip CF-Connecting-IP header within fetch

    In v4.15.0, Miniflare began stripping the CF-Connecting-IP header via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches the fetch API to strip the header during local wrangler dev sessions as a temporary workaround until the underlying issue is resolved.

  • Updated dependencies [f61a08e, ea71df3, d033a7d]:

4.15.0

Minor Changes

  • #8794 02f0699 Thanks @​eastlondoner! - This adds support for more accurate types for service bindings when running wrangler types. Previously, running wrangler types with a config including a service binding would generate an Env type like this:

    interface Env {
	SERVICE_BINDING: Fetcher;
}

    This type was "correct", but didn't capture the possibility of using JSRPC to communicate with the service binding. Now, running wrangler types -c wrangler.json -c ../service/wrangler.json (the first config representing the current Worker, and any additional configs representing service bound Workers) will generate an Env type like this:

    interface Env {
	SERVICE_BINDING: Service<import("../service/src/index").Entrypoint>;
}

  • #8716 63a6504 Thanks @​ItsWendell! - add --metafile flag to generate esbuild metadata file during build

  • #9122 f17ee08 Thanks @​avenceslau! - Unhide wrangler workflows delete command

Patch Changes

... (truncated)

Commits

Updates vitest from 2.1.9 to 3.1.3

Release notes

Sourced from vitest's releases.

v3.1.3

   🐞 Bug Fixes

    View changes on GitHub

v3.1.2

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v3.1.1

... (truncated)

Commits
  • 6e8d937 chore: release v3.1.3
  • 8c7f75a fix: ignore failures on writeToCache (#7893)
  • d613b81 fix(reporters): --merge-reports to show each total run times (#7877)
  • 2fa763a fix: reset mocks on test retry/repeat (#7897)
  • 573cb16 ci: fix flaky browser tests (#7887)
  • 03660f9 fix(browser): correctly inherit CLI options (#7858)
  • a83f3bf fix: correctly resolve vitest import if inline: true is set (#7856)
  • 5a0afd1 chore: release v3.1.2
  • b70a6f1 chore(deps): unbundle tinyglobby and update (#7864)
  • f9eacbc fix(vite-node): add ERR_MODULE_NOT_FOUND code error if module cannot be loade...
  • 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 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.

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 15, 2025
@dependabot dependabot bot requested a review from pyropy as a code owner May 15, 2025 16:42
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 15, 2025
@dependabot
Bump esbuild, @cloudflare/vitest-pool-workers, wrangler and vitest
62d30b6 
Bumps [esbuild](https://github.com/evanw/esbuild) to 0.25.4 and updates ancestor dependencies [esbuild](https://github.com/evanw/esbuild), [@cloudflare/vitest-pool-workers](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vitest-pool-workers), [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). These dependencies need to be updated together.


Updates `esbuild` from 0.17.19 to 0.25.4
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2023.md)
- [Commits](evanw/esbuild@v0.17.19...v0.25.4)

Updates `@cloudflare/vitest-pool-workers` from 0.5.33 to 0.8.29
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/vitest-pool-workers/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/@cloudflare/[email protected]/packages/vitest-pool-workers)

Updates `wrangler` from 3.92.0 to 4.15.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/[email protected]/packages/wrangler)

Updates `vitest` from 2.1.9 to 3.1.3
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v3.1.3/packages/vitest)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.25.4
  dependency-type: indirect
- dependency-name: "@cloudflare/vitest-pool-workers"
  dependency-version: 0.8.29
  dependency-type: direct:development
- dependency-name: wrangler
  dependency-version: 4.15.1
  dependency-type: direct:development
- dependency-name: vitest
  dependency-version: 3.1.3
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/multi-0d89354763 branch from 2f8cd40 to 62d30b6 Compare May 15, 2025 16:43
@meridian-robot meridian-robot merged commit 304f4b3 into main May 15, 2025
5 checks passed
@meridian-robot meridian-robot deleted the dependabot/npm_and_yarn/multi-0d89354763 branch May 15, 2025 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pyropy pyropy Awaiting requested review from pyropy pyropy is a code owner

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@meridian-robot