build(deps-dev): bump the npm group across 1 directory with 4 updates

[dependabot]

Bumps the npm group with 4 updates in the / directory: globals, svelte, typescript and wrangler.

Updates globals from 17.9.0 to 17.11.0

Release notes

Sourced from globals's releases.

v17.11.0

• Add react-native globals (#337) 61eafbf

---

sindresorhus/globals@v17.10.0...v17.11.0

v17.10.0

• Add GM_cookie to Greasemonkey globals (#349) f468407

---

sindresorhus/globals@v17.9.0...v17.10.0

Commits

• 8c59927 17.11.0
• 61eafbf Add react-native globals (#337)
• 7bed4af 17.10.0
• f468407 Add GM_cookie to Greasemonkey globals (#349)
• See full diff in compare view

Updates svelte from 5.56.8 to 5.56.9

Release notes

Sourced from svelte's releases.

svelte@5.56.9

Patch Changes

• fix: skip controlled each fast path while another batch is pending (#18625)

• fix: better whitespace handling inside printer (#18638)

• fix: don't duplicate comments in attributes (#18636)

• fix: preserve CSS comments in the AST printer (#18637)

Changelog

Sourced from svelte's changelog.

5.56.9

Patch Changes

• fix: skip controlled each fast path while another batch is pending (#18625)

• fix: better whitespace handling inside printer (#18638)

• fix: don't duplicate comments in attributes (#18636)

• fix: preserve CSS comments in the AST printer (#18637)

Commits

• 20b341f Version Packages (#18628)
• ee6dff8 fix: better whitespace handling inside printer (#18638)
• a1d5035 fix: preserve CSS comments in the AST printer (#18637)
• 3ed9db4 fix: don't duplicate comments in attributes (#18636)
• 26786e9 fix: skip controlled each fast path while another batch is pending (#18625)
• See full diff in compare view

Updates typescript from 6.0.3 to 7.0.2

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.

Updates wrangler from 4.120.1 to 4.122.0

Release notes

Sourced from wrangler's releases.

wrangler@4.122.0

Minor Changes

• #15123 d0c976c Thanks @​dependabot! - Detect Node.js compatibility from the compatibility date, now that nodejs_compat is enabled by default

  As of compatibility date 2026-08-04, workerd enables the nodejs_compat and nodejs_compat_v2 compatibility flags by default. Previously these tools only treated Node.js compatibility as enabled when one of those flags was listed explicitly, so a Worker on a compatibility date of 2026-08-04 or later without the flag would get Node.js APIs from the runtime but no Node.js polyfills from the bundler, and process.env could be substituted with an empty object at build time. They now resolve these flags the same way workerd does, and honour no_nodejs_compat to opt out.

  To keep Node.js compatibility switched off on a newer compatibility date, specify both no_nodejs_compat and no_nodejs_compat_v2, since each flag has its own default.

  @cloudflare/vitest-pool-workers needs nodejs_compat_v2 for its own test runner, so it continues to override a project that opts out of it. On a compatibility date that enables the flag anyway, it now drops the opt-out rather than adding the flag back, which workerd would reject — previously this stopped such a project from running any tests at all.

  wrangler types also no longer attributes its @types/node suggestion to "the nodejs_compat flag", which it can now make for Workers that do not set the flag at all.

Patch Changes

• #15123 d0c976c Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @​cloudflare/workers-types	^5.20260804.1	^5.20260811.1
  workerd	1.20260804.1	1.20260811.1

• #15148 0b82b15 Thanks @​jamesopstad! - Ignore a nodejs_compat compatibility flag that the compatibility date already enables

  workerd rejects a compatibility flag that its compatibility date enables by default, so a Worker configured with both a compatibility date of 2026-08-04 or later and nodejs_compat failed to start locally with "The compatibility flag nodejs_compat became the default as of 2026-08-04 so does not need to be specified anymore".

  The redundant nodejs_compat and nodejs_compat_v2 flags are now dropped when starting the runtime, which has no effect on the resulting Worker because the compatibility date enables both anyway. no_nodejs_compat and no_nodejs_compat_v2 still switch Node.js compatibility off, and a flag specified alongside its own opt-out is left alone so that workerd still reports those as contradictory.

• #15123 d0c976c Thanks @​dependabot! - Stop adding a redundant nodejs_compat flag to generated Wrangler configurations

  create-cloudflare and wrangler setup write today's date as the compatibility_date, and from 2026-08-04 that already enables nodejs_compat. Adding the flag as well made the generated project fail to start with "The compatibility flag nodejs_compat became the default as of 2026-08-04 so does not need to be specified anymore", so the flag is now only added for earlier compatibility dates.

  create-cloudflare also removes the flag when a template, or a framework's own scaffolder, already wrote it into a configuration that ends up using such a compatibility date, and still installs @types/node for these projects even though there is no longer a flag to detect them by.

  wrangler setup does the same for a wrangler.json(c) that is already in the project: it writes today's date over whatever date that configuration was written for, so a nodejs_compat it finds there is removed as part of writing the file.

• #15142 3b02915 Thanks @​penalosa! - Fix remote binding sessions reusing stale binding configurations

  Starting a new remote bindings session that reuses a Worker name no longer picks up the bindings from a previous session, which could cause Binding "..." not found errors.

• Updated dependencies [d0c976c, d0c976c, 0b82b15, d0c976c, 90dd5e5]:

  • miniflare@5.20260811.0-alpha

wrangler@4.121.0

Minor Changes

• #15079 15cad03 Thanks @​podonnell-dev! - Add Preview base config secret commands

... (truncated)

Commits

• e5d56e9 Version Packages (#15145)
• 3b02915 [wrangler] Avoid stale remote binding sessions (#15142)
• d0c976c Bump the workerd-and-workers-types group across 1 directory with 2 updates (#...
• 15fc568 Version Packages (#15118)
• 5b1b930 Fetch script metadata directly instead of listing all scripts (#15132)
• 0aa8fa5 Support DO_NOT_TRACK=1 (#14924)
• 731b33a [wrangler] Allow test harness to reuse dry-run output (#15000)
• e1b5b4b feat(wrangler): add email.sending event subscription source (#14737)
• 6e7d37d [wrangler] Fix modules-watch-stub injection when bundle:false (fixes … (#15032)
• 026e058 WC-5699 adjust preview deploy output (#15081)
• 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 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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.