chore(deps-dev): bump typescript from 5.9.3 to 6.0.3

[dependabot]

Bumps 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

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	docs-preview	bd7b39c	May 13 2026, 03:46 PM

[jrphilo]

Ralphie skipped this for: skip-needs-review (build-tooling major, elevated scrutiny)

What I saw: pnpm build fails on this branch with Cannot find module or type declarations for side-effect import of '@/styles/tailwind.css' at src/app/layout.tsx:19. TypeScript 6.0 flips the noUncheckedSideEffectImports compiler default from false to true — a documented breaking change in the TS 6.0 announcement. pnpm install --frozen-lockfile and pnpm check:links were clean; pnpm lint could not be evaluated cleanly in the worktree (sibling-eslintrc conflict, unrelated to the bump).

What I investigated:

• Ownership / supply-chain: still Microsoft (pnpm view typescript@6.0.3 — maintainers microsoft1es, typescript-bot, weswigham, andrewbranch, etc.; Apache-2.0; zero runtime deps). No supply-chain concerns.
• Other TS 6.0 default flips against our tsconfig.json: strict (already true), module: esnext (already), target: es6 (still valid; only es5 removed), moduleResolution: bundler (not deprecated), lib: ["dom","dom.iterable","esnext"] (dom.iterable is now an empty stub merged into dom — harmless), no baseUrl, esModuleInterop: true. No other removed features in use (no AMD/UMD/SystemJS, no --outFile, no classic resolution, no module Foo {} namespaces, no assert-style import assertions).
• Side-effect imports across the repo: only two — import '@/styles/tailwind.css' in src/app/layout.tsx (the failure) and import 'server-only' in src/lib/source.ts (server-only ships its own types — fine). The CSS import is the only regression surface.
• pnpm check:links clean (39 files, 3 internal links, 0 broken).

What's still unclear: the minimal mechanical fix is small (either an ambient declare module '*.css' in a src/types/*.d.ts, or set noUncheckedSideEffectImports: false in tsconfig.json, or add "ignoreDeprecations": "6.0"), but as a TypeScript major under elevated scrutiny there's a judgment call to make: (a) which fix is preferred for this repo, and (b) whether to adopt TS 6.0 at all yet — the 6.0.3 release is only ~3 weeks old and subtle type-narrowing regressions in untested code branches can't be fully ruled out from a clean Next.js build alone.

What would unblock it: maintainer picks the fix approach (ambient CSS declaration vs. tsconfig flag) and confirms readiness to adopt TS 6.0; remove the ralphie:skip-needs-review label to re-queue, or close in favor of a hand-crafted upgrade PR.