Adopt stable TypeScript 7 across the workspace - #38
Merged
Conversation
Replace the native preview tool with the stable TypeScript 7 package and run type checks through tsc. Upgrade tsdown for TypeScript 7 support and give declaration builds repository-root configs so workspace source paths do not leak generated declarations into package sources. User Prompt: Now that TypeScript 7 has been officially released, replace the separately installed tsgo preview with the official TypeScript 7 package throughout the monorepo. Assisted-by: Codex:gpt-5.6-sol
dahlia
added
bug
sij411
approved these changes
Jul 28, 2026
2chanhaeng
approved these changes
Jul 28, 2026
github-project-automation
Bot
moved this from In progress
to Done
in NLnet NGI0 Commons Fund (2026)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TypeScript 7 makes the native compiler the supported implementation behind the
typescriptpackage. Keeping@typescript/native-previewin mise.toml would leave type checking on a dated preview build while the workspace still declared TypeScript 6. The compiler should instead come from the same dependency graph as the code it checks.The catalog in pnpm-workspace.yaml now selects TypeScript 7.0.2. Every package that participates in recursive type checking has a direct catalog dependency, including packages/web/package.json, so
pnpm --recursive exec tsc --noEmitdoes not depend on a globally installed preview binary. tsdown moves to 0.22.14 because that release recognizes the stable TypeScript 7 package and declares support for it.Keep declaration emission inside the workspace
The native declaration compiler exposed a boundary hidden by the preview setup. The GraphQL and application packages map workspace dependencies directly to sibling source trees. When tsdown starts declaration generation with a package-local config, those sources fall outside the root chosen by
rolldown-plugin-dts, which can leave generated declarations beside files in packages/models/src/ and packages/graphql/src/.The dedicated tsconfig.models.json, tsconfig.graphql.json, and tsconfig.drfed.json files give declaration generation the repository root as its boundary. Each one still extends its package config and narrows
includeto the package being built. ItstypeRootspoints back to that package's installed Node.js types, preserving the package-local dependency boundary even though the config itself lives at the root. This keeps tsdown's published .d.mts layout unchanged without allowing temporary declarations into source directories.Keep one lockfile authoritative
The pnpm workspace already resolves all four packages through the root pnpm-lock.yaml. Keeping packages/web/pnpm-lock.yaml alongside it allowed the web package to describe a second dependency graph with different resolutions. Removing the nested lockfile makes the regenerated root lockfile the only record of the TypeScript and tsdown upgrade.