build(deps): bump the typescript group across 1 directory with 3 updates

[dependabot]

Bumps the typescript group with 3 updates in the / directory: typescript, @types/node and @types/debug.

Updates typescript from 5.9.3 to 6.0.3

Release notes

Sourced from typescript's releases.

TypeScript 6.0.3

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).
• fixed issues query for TypeScript 6.0.3 (Stable).

Downloads are available on:

• npm

TypeScript 6.0

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).

Downloads are available on:

• npm

TypeScript 6.0 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 6.0.0 (Beta).

Downloads are available on:

• npm

Commits

• 050880c Bump version to 6.0.3 and LKG
• eeae9dd 🤖 Pick PR #63401 (Also check package name validity in...) into release-6.0 (#...
• ad1c695 🤖 Pick PR #63368 (Harden ATA package name filtering) into release-6.0 (#63372)
• 0725fb4 🤖 Pick PR #63310 (Mark class property initializers as...) into release-6.0 (#...
• 607a22a Bump version to 6.0.2 and LKG
• 9e72ab7 🤖 Pick PR #63239 (Fix missing lib files in reused pro...) into release-6.0 (#...
• 35ff23d 🤖 Pick PR #63163 (Port anyFunctionType subtype fix an...) into release-6.0 (#...
• e175b69 Bump version to 6.0.1-rc and LKG
• af4caac Update LKG
• 8efd7e8 Merge remote-tracking branch 'origin/main' into release-6.0
• Additional commits viewable in compare view

Updates @types/node from 25.5.0 to 25.7.0

Commits

• See full diff in compare view

Updates @types/debug from 4.1.12 to 4.1.13

Commits

• See full diff in compare view

[github-actions]

ℹ️ This PR updates development dependencies with major version changes. Please review for potential breaking changes in the build/test pipeline.

[wpmobilebot]

📊 Performance Test Results

Comparing fe05ddd vs trunk

app-size

Metric	trunk	fe05ddd	Diff	Change
App Size (Mac)	1355.48 MB	1355.48 MB	+0.00 MB	⚪ 0.0%

site-editor

Metric	trunk	fe05ddd	Diff	Change
load	1484 ms	1497 ms	+13 ms	⚪ 0.0%

site-startup

Metric	trunk	fe05ddd	Diff	Change
siteCreation	8566 ms	8591 ms	+25 ms	⚪ 0.0%
siteStartup	4937 ms	4929 ms	8 ms	⚪ 0.0%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

[github-actions]

ℹ️ This PR updates development dependencies with major version changes. Please review for potential breaking changes in the build/test pipeline.

[github-actions]

ℹ️ This PR updates development dependencies with major version changes. Please review for potential breaking changes in the build/test pipeline.

[github-actions]

ℹ️ This PR updates development dependencies with major version changes. Please review for potential breaking changes in the build/test pipeline.

[github-actions]

ℹ️ This PR updates development dependencies with major version changes. Please review for potential breaking changes in the build/test pipeline.

[wojtekn]

The dependabot TS 5.9 → 6.0 bump surfaces two deprecations that stop functioning in TS 7.0:

• baseUrl - straightforward. The migration is documented (drop baseUrl, prepend its value to each paths entry)
• moduleResolution: "node" (alias for node10) - this is the open question. The non-deprecated replacements are node16, nodenext, or bundler, but none is a drop-in:
  • node16 surfaces ~50 real errors: type-only ESM-from-CJS imports needing resolution-mode attributes, relative imports needing explicit .js extensions, plus declaration gaps in @wp-playground/blueprints and wpcom/types. Also requires module: "node16", which we can't fully adopt because we use __dirname / require() in apps/studio.
  • bundler is cleaner (no extension/ESM-interop noise) but still fails on @wp-playground/blueprints (package's exports map has no types condition, and the CJS index.cjs has no adjacent .d.cts) and wpcom/types (subpath not declared in exports). Both are dependency packaging issues, not our code.

We could migrate baseUrl and use ignoreDeprecations for moduleResolution for now. @Automattic/yolo any thoughts?

[fredrikekelund]

I'm looking at how we can tweak the configs to actually fix the deprecations. The things that Typescript v6 deprecates will stop working in Typescript v7, and upgrading to v7 when it's released is really appealing (because of the performance boost)

[wojtekn]

@fredrikekelund sounds great. FYI, I pushed a fix for baseUrl for now.

[fredrikekelund]

I had to actually try some stuff to see what worked, and I went ahead and committed and pushed the changes.

Every workspace now has a module and moduleResolution setting. module is typically es2022, and moduleResolution is typically bundler. module: es2022 suits us because we write our imports effectively using ESM (docs). moduleResolution: bundler suits us because we run a bundler in every workspace that generates production code.

Moreover, I swapped ts-node for tsx, because I kept running into import-related errors with ts-node. tsx uses esbuild under the hood, so module loading works more like it does in our production code, which is also bundled.

I confirmed that type checking passes, that the app starts, and that it can spawn the CLI. If the E2E tests pass, then we should be able to land this

[wojtekn]

@fredrikekelund nice, that looks great.

[fredrikekelund]

E2E tests passing. I'll land this 👍