Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adm01-debug merged 1 commit into from
May 9, 2026
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -182,7 +182,7 @@
"tailwindcss": "^3.4.19",
"tailwindcss-animate": "^1.0.7",
"tsx": "^4.21.0",
"typescript": "^5.5.3",
"typescript": "^6.0.3",
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot May 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

For @typescript-eslint/parser8.18.0 and@typescript-eslint/eslint-plugin 8.18.0, what TypeScript versions are officially supported? Does the support range include TypeScript 6.0.x?

💡 Result:

For @typescript-eslint/parser 8.18.0 and @typescript-eslint/eslint-plugin 8.18.0, the officially supported TypeScript versions are >=4.8.4 and <5.8.0.[1][2] This is indicated by the peer dependency range in the parser's package.json ("typescript": ">=4.8.4 <5.8.0"), which the plugin shares via shared internals like @typescript-eslint/typescript-estree.[3][4] The parser warns on unsupported versions, with examples showing ranges like >=4.7.4 <5.7.0 in nearby versions, confirming the pattern of supporting recent TS versions (less than 2 years old).[3][4] TypeScript 6.0.x is not supported, as it exceeds the upper bound <5.8.0; support for TS 6 was added later in v8.58.0.[5][6]

Citations:

🌐 Web query:

Does Vite 5.4.19 (and @vitejs/plugin-react-swc 3.11.0) officially support TypeScript 6.0.x in type-checking and development workflows?

💡 Result:

No—there is no official statement from Vite 5.4.19 or @vitejs/plugin-react-swc 3.11.0 that they “support TypeScript 6.0.x” specifically for type-checking and development workflows. Why: 1) Vite itself does not perform TypeScript type checking; it only transpiles TypeScript files, and it explicitly notes that type checking is handled by your IDE/build process, not by Vite. So any “type-checking support” is not something Vite claims for any particular TypeScript version (including 6.0.x) [1]. 2) The official Vite plugin page for TypeScript behavior indicates transpilation-only behavior and discusses tsconfig handling, but it does not claim compatibility guarantees with a specific TypeScript major/minor range [1]. 3) The official @vitejs/plugin-react-swc documentation we found describes behavior/limits (e.g., tsconfig not resolved; target ignored and defaults used), but we did not find any official peer dependency or stated TypeScript version range that explicitly includes TypeScript 6.0.x [2]. What we can confirm from authoritative sources we found: - Vite 5.4.19 exists as a release (but the release notes/changelog we saw are about other fixes, not TypeScript 6 compatibility) [3][4]. - The Vite core repository later includes an internal/template change upgrading TypeScript to 6 (commit/issues from 2026-04), which suggests ecosystem movement toward TS 6, but it is not an explicit claim that Vite 5.4.19 (or plugin 3.11.0) officially supports TS 6.0.x in the specific way you asked [5][6]. Conclusion: Based on the official docs we located, Vite 5.4.19 and @vitejs/plugin-react-swc 3.11.0 do not “officially support TypeScript 6.0.x in type-checking workflows” (because Vite doesn’t do type checking) and we also did not find an official compatibility guarantee specifically naming TS 6.0.x for those versions [1][2]. If you want, tell me whether your workflow uses (a) IDE-only type checking (tsserver), (b) tsc --noEmit, (c) vite type-checking via a separate tool (e.g., vue-tsc / eslint), or (d) testing tools, and I can research which part of the toolchain needs TS 6 support.

Citations:

@typescript-eslint 8.18.0 does not support TypeScript 6.0.3—upgrade to 8.58.0+ or downgrade TypeScript.

TypeScript 6.0.3 requires @typescript-eslint/parser and @typescript-eslint/eslint-plugin v8.58.0 or later. The pinned version 8.18.0 only supports TypeScript >=4.8.4 <5.8.0, which excludes TS 6.0.x. Since your lint and typecheck scripts both run tsc --noEmit, this incompatibility will cause failures. Either upgrade both ESLint-TypeScript packages to ^8.58.0+ or pin TypeScript to ^5.4 instead.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 178, The package.json currently pins "typescript":
"^6.0.3" which is incompatible with the installed `@typescript-eslint` v8.18.0;
update package.json to fix the mismatch by either upgrading both
`@typescript-eslint/parser` and `@typescript-eslint/eslint-plugin` to >=8.58.0
(recommended) or by downgrading "typescript" to a supported ^5.x (e.g., ^5.4);
ensure you update the corresponding devDependencies entries for
"@typescript-eslint/parser" and "@typescript-eslint/eslint-plugin" when choosing
the upgrade path and run npm/yarn install and your lint/typecheck scripts to
verify.

"vite": "^5.4.19"
},
"packageManager": "npm@10.9.7",
Expand Down
Loading