Bump the npm_and_yarn group across 1 directory with 4 updates #1

dependabot · 2025-08-09T13:17:00Z

Bumps the npm_and_yarn group with 4 updates in the / directory: esbuild, vite, vite-plugin-pwa and wrangler.

Updates esbuild from 0.17.19 to 0.25.8

Release notes

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:
class CachedDict {
  #has = (a: string) => dict.has(a);
  has = window
    ? (word: string): boolean => this.#has(word)
    : this.#has;
}
Fix a regression with the parsing of source phase imports

The change in the previous release to parse source phase imports failed to properly handle the following cases:
import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'
Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.
v0.25.7
Parse and print JavaScript imports with an explicit phase (#4238)

This release adds basic syntax support for the defer and source import phases in JavaScript:
defer

This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:
import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");
Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".
source

This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:
import source foo from "<specifier>";
const bar = await import.source("<specifier>");

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

8c71947 publish 0.25.8 to npm
0508f24 some parsing fixes for source phase imports
6e4be2f js parser: recover from bad #private identifiers
c9c6357 fix #4248: #private ids in arrow fn body in ?:
9b42f68 publish 0.25.7 to npm
9ba01d1 abs-paths: js api and tests
ca196c9 fix for parser backtracking crash
2979b84 fix #4241: ts arrow function type backtrack (hack)
1180410 fix an unused variable warning
fc3da57 fix #4238: add defer and source import phases
Additional commits viewable in compare view

Updates vite from 5.4.19 to 7.1.1

Release notes

Sourced from vite's releases.

v7.1.1

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

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.

[email protected]

Please refer to CHANGELOG.md for details.

v7.0.2

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

v7.0.1

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

[email protected]

Please refer to CHANGELOG.md for details.

... (truncated)

Changelog

Sourced from vite's changelog.

7.1.1 (2025-08-08)

Bug Fixes

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

Miscellaneous Chores

fix changelog beta links (#20561) (2e0c21a)

update 7.1 changelog (#20560) (d8869b8)

7.1.0 (2025-08-07)

Features

support files with more than 1000 lines by generateCodeFrame (#20508) (e7d0b2a)

add import.meta.main support in config (bundle config loader) (#20516) (5d3e3c2)

optimizer: improve dependency optimization error messages with esbuild formatMessages (#20525) (d17cfed)

ssr: add import.meta.main support for Node.js module runner (#20517) (794a8f2)

add future: 'warn' (#20473) (e6aaf17)

add removeServerPluginContainer future deprecation (#20437) (c1279e7)

add removeServerReloadModule future deprecation (#20436) (6970d17)

add server.warmupRequest to future deprecation (#20431) (8ad388a)

add ssrFixStacktrace / ssrRewriteStacktrace to removeSsrLoadModule future deprecation (#20435) (8c8f587)

client: ping from SharedWorker (#19057) (5c97c22)

dev: add this.fs support (#20301) (0fe3f2f)

export defaultExternalConditions (#20279) (344d302)

implement removePluginHookSsrArgument future deprecation (#20433) (95927d9)

implement removeServerHot future deprecation (#20434) (259f45d)

resolve server URLs before calling other listeners (#19981) (45f6443)

ssr: resolve externalized packages with resolve.externalConditions and add module-sync to default external condition (#20409) (c669c52)

ssr: support import.meta.resolve in module runner (#20260) (62835f7)

Bug Fixes

css: avoid warnings for image-set containing __VITE_ASSET__ (#20520) (f1a2635)

css: empty CSS entry points should generate CSS files, not JS files (#20518) (bac9f3e)

dev: denied request stalled when requested concurrently (#20503) (64a52e7)

manifest: initialize entryCssAssetFileNames as an empty Set (#20542) (6a46cda)

skip prepareOutDirPlugin in workers (#20556) (97d5111)

asset: only watch existing files for new URL(, import.meta.url) (#20507) (1b211fd)

client: keep ping on WS constructor error (#20512) (3676da5)

deps: update all non-major dependencies (#20537) (fc9a9d3)

don't resolve as relative for specifiers starting with a dot (#20528) (c5a10ec)

html: allow control character in input stream (#20483) (c12a4a7)

merge old and new noExternal: true correctly (#20502) (9ebe4a5)

deps: update all non-major dependencies (#20489) (f6aa04a)

dev: denied requests overly (#20410) (4be5270)

hmr: register css deps as type: asset (#20391) (7eac8dd)

optimizer: discover correct jsx runtime during scan (#20495) (10d48bb)

preview: set correct host for resolvedUrls (#20496) (62b3e0d)

worker: resolve WebKit compat with inline workers by deferring blob URL revocation (#20460) (8033e5b)

... (truncated)

Commits

f4438a1 release: v7.1.1
826b394 fix(deps): update launch-editor-middleware (#20569)
2e0c21a chore: fix changelog beta links (#20561)
d8869b8 chore: update 7.1 changelog (#20560)
931684e release: v7.1.0
97d5111 fix: skip prepareOutDirPlugin in workers (#20556)
1f23554 test: fix unimportant errors in test-unit (#20545)
856d3f0 test: detect ts support via process.features (#20544)
f1a2635 fix(css): avoid warnings for image-set containing __VITE_ASSET__ (#20520)
6a46cda fix(manifest): initialize entryCssAssetFileNames as an empty Set (#20542)
Additional commits viewable in compare view

Updates vite-plugin-pwa from 0.17.5 to 1.0.2

Release notes

Sourced from vite-plugin-pwa's releases.

v1.0.2

   🚀 Features

pwa-assets: Add additional checks to resolve images - by @userquin in vite-pwa/vite-plugin-pwa#876 (03404)

    View changes on GitHub

v1.0.1

   🐞 Bug Fixes

Added vite 7.0.0 support - by @hasanparasteh in vite-pwa/vite-plugin-pwa#868 (34229)

    View changes on GitHub

v1.0.0

   🚨 Breaking Changes

Update @vite-pwa/assets-generator to v1.0.0 - by @userquin in vite-pwa/vite-plugin-pwa#846 (1c570)

   🐞 Bug Fixes

Avoid assigning to bundle object - by @sapphi-red in vite-pwa/vite-plugin-pwa#843 (b0716)

    View changes on GitHub

v0.21.2

   🐞 Bug Fixes

manifest: Default manifest theme_color and description not being applied - by @alexandre-hallaine in vite-pwa/vite-plugin-pwa#839 (53568)

    View changes on GitHub

v0.21.1

   🚀 Features

Support Vite 6 - by @gabrielrbarbosa and @userquin in vite-pwa/vite-plugin-pwa#797 (c4c25)

html: Add head when missing from entry point - by @userquin in vite-pwa/vite-plugin-pwa#784 (856d3)

   🐞 Bug Fixes

Do not await workbox-window messageSkipWaiting - by @piotr-cz in vite-pwa/vite-plugin-pwa#795 (f5197)

Return async function from registerSW in dev mode - by @piotr-cz in vite-pwa/vite-plugin-pwa#799 (06c1d)

    View changes on GitHub

v0.21.0

   🚨 Breaking Changes

Update workbox to 7.3.0 - by @userquin in vite-pwa/vite-plugin-pwa#781 (e01e4)

... (truncated)

Commits

4385f0a chore: release v1.0.2
9b650a1 chore: update pnpm to v10.13.1
0340498 feat(pwa-assets): add additional checks to resolve images (#876)
9fd1a03 chore: release v1.0.1
1967829 chore: update pnpm to v10.12.4 (#870)
3422925 fix: added vite 7.0.0 support (#868)
92eca1b chore: release v1.0.0
1c570fb feat!: update @vite-pwa/assets-generator to v1.0.0 (#846)
b07167f fix: avoid assigning to bundle object (#843)
11923f3 chore: release v0.21.2
Additional commits viewable in compare view

Updates wrangler from 3.114.13 to 4.28.1

Release notes

Sourced from wrangler's releases.

[email protected]

Patch Changes
#10130 773cca3 Thanks @dario-piotrowicz! - update maybeStartOrUpdateRemoteProxySession config argument (to allow callers to specify an environment)

Before this change maybeStartOrUpdateRemoteProxySession could be called with either the path to a wrangler config file or the configuration of a worker. The former override however did not allow the caller to specify an environment, so the maybeStartOrUpdateRemoteProxySession API has been updated so that in the wrangler config case an object (with the path and a potential environment) needs to be passed instead.

For example, before callers could invoke the function in the following way
await maybeStartOrUpdateRemoteProxySession(configPath);
note that there is no way to tell the function what environment to use when parsing the wrangle configuration.

Now callers will instead call the function in the following way:
await maybeStartOrUpdateRemoteProxySession({
	path: configPath,
	environment: targetEnvironment,
});
note that now a target environment can be specified.
#10130 773cca3 Thanks @dario-piotrowicz! - fix getPlatformProxy not taking into account the potentially specified environment for remote bindings
#10122 2e8eb24 Thanks @dario-piotrowicz! - fix startWorker not respecting auth options for remote bindings

fix startWorker currently not taking into account the auth field that can be provided as part of the dev options when used in conjunction with remote bindings

example:

Given the following
import { unstable_startWorker } from "wrangler";
const worker = await unstable_startWorker({
entrypoint: "./worker.js",
bindings: {
AI: {
type: "ai",
experimental_remote: true,
},
},
dev: {

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.28.1

Patch Changes
#10130 773cca3 Thanks @dario-piotrowicz! - update maybeStartOrUpdateRemoteProxySession config argument (to allow callers to specify an environment)

Before this change maybeStartOrUpdateRemoteProxySession could be called with either the path to a wrangler config file or the configuration of a worker. The former override however did not allow the caller to specify an environment, so the maybeStartOrUpdateRemoteProxySession API has been updated so that in the wrangler config case an object (with the path and a potential environment) needs to be passed instead.

For example, before callers could invoke the function in the following way
await maybeStartOrUpdateRemoteProxySession(configPath);
note that there is no way to tell the function what environment to use when parsing the wrangle configuration.

Now callers will instead call the function in the following way:
await maybeStartOrUpdateRemoteProxySession({
	path: configPath,
	environment: targetEnvironment,
});
note that now a target environment can be specified.
#10130 773cca3 Thanks @dario-piotrowicz! - fix getPlatformProxy not taking into account the potentially specified environment for remote bindings
#10122 2e8eb24 Thanks @dario-piotrowicz! - fix startWorker not respecting auth options for remote bindings

fix startWorker currently not taking into account the auth field that can be provided as part of the dev options when used in conjunction with remote bindings

example:

Given the following
import { unstable_startWorker } from "wrangler";
const worker = await unstable_startWorker({
entrypoint: "./worker.js",
bindings: {
AI: {
type: "ai",
experimental_remote: true,
},
},

... (truncated)

Commits

d16de46 Version Packages (#10223)
93c4c26 fix: strip ANSI escape codes from wrangler log files (#10209)
2e8eb24 fix startWorker not respecting auth options for remote bindings (#10122)
773cca3 fix specified environments being ignored for remote bindings in some cases (#...
48853a6 validate container configuration in wrangler (#9774)
5bd0a19 stop vitest pool workers breaking when containers are present (#10162)
390b7fb Version Packages (#10156)
ab59066 Move macOS version validation from @cloudflare/cli to miniflare (#10211)
dae1377 WC-3776 Require confirm for delete when Pages project binds to worker (#10186)
43b6f7b chore: rename old mixed-mode references to remote-bindings (#10134)
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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
You can disable automated security fix PRs for this repo from the Security Alerts page.

github-advanced-security · 2025-08-09T13:18:48Z

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

Bumps the npm_and_yarn group with 4 updates in the / directory: [esbuild](https://github.com/evanw/esbuild), [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite), [vite-plugin-pwa](https://github.com/vite-pwa/vite-plugin-pwa) and [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler). Updates `esbuild` from 0.17.19 to 0.25.8 - [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.8) Updates `vite` from 5.4.19 to 7.1.1 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.1.1/packages/vite) Updates `vite-plugin-pwa` from 0.17.5 to 1.0.2 - [Release notes](https://github.com/vite-pwa/vite-plugin-pwa/releases) - [Commits](vite-pwa/vite-plugin-pwa@v0.17.5...v1.0.2) Updates `wrangler` from 3.114.13 to 4.28.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) --- updated-dependencies: - dependency-name: esbuild dependency-version: 0.25.8 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: vite dependency-version: 7.1.1 dependency-type: direct:development dependency-group: npm_and_yarn - dependency-name: vite-plugin-pwa dependency-version: 1.0.2 dependency-type: direct:development dependency-group: npm_and_yarn - dependency-name: wrangler dependency-version: 4.28.1 dependency-type: direct:development dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <[email protected]>

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 9, 2025

dependabot bot force-pushed the dependabot/npm_and_yarn/npm_and_yarn-b600ead08c branch from d0cb0bd to 95373d6 Compare August 9, 2025 13:51

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Bump the npm_and_yarn group across 1 directory with 4 updates #1

Bump the npm_and_yarn group across 1 directory with 4 updates #1

Uh oh!

dependabot bot commented on behalf of github Aug 9, 2025 •

edited

Loading

Uh oh!

github-advanced-security bot commented Aug 9, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Bump the npm_and_yarn group across 1 directory with 4 updates #1

Are you sure you want to change the base?

Bump the npm_and_yarn group across 1 directory with 4 updates #1

Uh oh!

Conversation

dependabot bot commented on behalf of github Aug 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

v0.25.8

v0.25.7

Changelog: 2023

0.19.11

v7.1.1

v7.1.0

v7.1.0-beta.1

v7.1.0-beta.0

v7.0.6

v7.0.5

v7.0.4

v7.0.3

v7.0.2

v7.0.1

7.1.1 (2025-08-08)

Bug Fixes

Miscellaneous Chores

7.1.0 (2025-08-07)

Features

Bug Fixes

v1.0.2

🚀 Features

v1.0.1

🐞 Bug Fixes

v1.0.0

🚨 Breaking Changes

🐞 Bug Fixes

v0.21.2

🐞 Bug Fixes

v0.21.1

🚀 Features

🐞 Bug Fixes

v0.21.0

🚨 Breaking Changes

Patch Changes

4.28.1

Patch Changes

Uh oh!

github-advanced-security bot commented Aug 9, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

dependabot bot commented on behalf of github Aug 9, 2025 •

edited

Loading