feat: bump typescript 5.9.3 → 6.0.3#25
Merged
Merged
Conversation
Closes #20. - typescript: 5.9.3 → 6.0.3 across all 11 workspace package.jsons - tsconfig.base.json: add `"types": ["node"]` The `types` addition is the one mandatory fix for TS 6. Starting in 6.0, the default `types` value flipped from "every package under node_modules/@types" to `[]`. Without an explicit entry, `@types/node` is no longer auto-loaded and `node:*` module specifiers fail to resolve (surfacing as the misleading `TS2591: Cannot find name 'node:assert/strict'`). Peer-compat sweep: the issue flagged tree-sitter grammars as a risk for `typescript@^5` peer-range violations. None of them declare typescript as a peer dependency — they're runtime parsers, not language-service plugins. No peer overrides needed. Verified locally: - pnpm -r build: clean - pnpm -r exec tsc --noEmit: clean - pnpm -r test: 952 pass / 0 fail - biome ci, banned-strings, license-checker: green
theagenticguy
force-pushed
the
feat/typescript-6
branch
from
8dca435 to
dd256d8
Compare
Closed
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
1 participant
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.
Summary
Closes #20.
typescript→6.0.3across all 11 workspacepackage.jsonstsconfig.base.json: add"types": ["node"]The one mandatory fix
TypeScript 6.0 flipped the default of
compilerOptions.typesfrom "every package undernode_modules/@types" to[]. Without an explicit entry,@types/nodeis no longer auto-loaded andnode:*module specifiers fail to resolve — surfacing as the misleading error:Adding
"types": ["node"]once intsconfig.base.jsonflows through every workspace viaextends. If any package later needs extras (e.g.vitest/globals), it overridestypeslocally —typesdoesn't merge acrossextends.Peer-compat sweep
The issue flagged tree-sitter grammars,
@apidevtools/swagger-parser,@modelcontextprotocol/sdk,zod,piscina, etc. as possible peer-range risks. Checked withnpm view <pkg> peerDependencies.typescript:tree-sitter,tree-sitter-typescript,tree-sitter-python,tree-sitter-c,tree-sitter-java,tree-sitter-rust,web-tree-sitter— none declare typescript as a peer. They're runtime parsers, not language-service plugins.typescriptpeer.No peer overrides needed.
Test plan
pnpm -r buildcleanpnpm -r exec tsc --noEmitcleanpnpm -r test→ 952 pass / 0 failbiome ci .clean (52 warnings / 485 infos are pre-existing)bash scripts/check-banned-strings.shcleanlicense-checker-rseidelsohnclean