Skip to content

chore: Upgrade TypeScript toolchain to 6.0.3#1359

Closed
mrousavy wants to merge 1 commit into
mainfrom
chore/upgrade-typescript-6.0.3
Closed

chore: Upgrade TypeScript toolchain to 6.0.3#1359
mrousavy wants to merge 1 commit into
mainfrom
chore/upgrade-typescript-6.0.3

Conversation

@mrousavy

Copy link
Copy Markdown
Owner

Summary

  • upgrade root/template TypeScript pins to 6.0.3
  • upgrade typescript-eslint to 8.60.0, whose peer range supports TypeScript <6.1
  • upgrade @tsconfig/react-native to 3.0.9
  • remove local TS 6 deprecated config options by switching repo-owned configs from moduleResolution: node to moduleResolution: bundler and dropping noImplicitUseStrict / noStrictGenericChecks

Notes

TypeScript 6.0 deprecates baseUrl, moduleResolution: node, and several legacy compiler flags ahead of TypeScript 7. This PR fixes the config entries owned by this repo instead of adding a broad ignoreDeprecations setting.

The docs workspace stays on its current TypeScript pin in this PR because Docusaurus 3.8's inherited tsconfig still contains baseUrl; the Docusaurus upgrade PR handles that stack together.

Validation

  • bun install --ignore-scripts
  • bun run typecheck
  • bun run build
  • bun nitro lint-ci
  • bun nitrogen lint-ci
  • bun nitro-test lint-ci
  • bun nitro-test-external lint-ci
  • bun example lint-ci
  • bun tsc -p packages/template/tsconfig.json --noEmit
  • git diff --check

@vercel

vercel Bot commented May 27, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
nitro-docs Ready Ready Preview, Comment May 28, 2026 10:13am

Request Review

@mrousavy

Copy link
Copy Markdown
Owner Author

Superseded by #1362, which folds the remaining package upgrades into a single PR.

@mrousavy mrousavy closed this May 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant