Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
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
88 changes: 60 additions & 28 deletions web/package-lock.json

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

2 changes: 1 addition & 1 deletion web/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@
"@types/react-dom": "^19.2.3",
"@vitejs/plugin-react": "^5.1.1",
"rollup-plugin-visualizer": "6.0.3",
"typescript": "~5.9.3",
"typescript": "~6.0.3",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

TypeScript 6.0 release notes breaking changes

💡 Result:

TypeScript 6.0, released on March 23, 2026, serves as a significant transition release designed to prepare developers for TypeScript 7.0, which will introduce a native port of the compiler [1][2][3]. While TypeScript 6.0 maintains API compatibility with version 5.9, it introduces several breaking changes and deprecations [1][2]. Important Migration Note: To ease the transition, deprecations in TypeScript 6.0 can be temporarily ignored by setting "ignoreDeprecations": "6.0" in your tsconfig.json [1][2][4]. However, these options will be removed entirely in TypeScript 7.0 [1][5]. Key Breaking Changes and Default Shifts: - Strict Mode: "strict" now defaults to true [1][2][6]. - Module Format: "module" now defaults to "esnext" [3][6]. - ECMAScript Target: "target" now defaults to "es2025" [3][6]. - Module Resolution: "moduleResolution" now defaults to "bundler" [3]. The "classic" resolution strategy is removed entirely [6]. - Type Defaults: "types" now defaults to an empty array ([]) [1][2][6]. - Project Root: "rootDir" now defaults to the directory containing your tsconfig.json, rather than the computed source root [3][6][5]. - Library Imports: "noUncheckedSideEffectImports" now defaults to true [3][6]. - Import Settings: "esModuleInterop" and "allowSyntheticDefaultImports" are now always enabled [2][6]. Deprecated Features: The following features are deprecated and will be removed in TypeScript 7.0 [1][2]: - target: "es5" [1][2][6] - --moduleResolution node (use "node10" or "bundler" instead) [1][2][5] - --moduleResolution classic [1][2][6] - --downlevelIteration [2] - --baseUrl [2][5] - --esModuleInterop false and --allowSyntheticDefaultImports false [2] - --alwaysStrict false [2][5] - outFile [2][5] - asserts keyword on imports [2][5] - no-default-lib directives [2][5] Additionally, using AMD, UMD, or System module formats will now trigger compiler errors [6]. Specifying files via the command line when a tsconfig.json exists is also now an error [5].

Citations:


🏁 Script executed:

#!/bin/bash
# Description: Run typecheck with TypeScript 6.0.3 to verify compatibility

cd web && npm install && npm run typecheck

Repository: Pythoughts-labs/pythinker-code

Length of output: 890


TypeScript 6.x bump breaks web typecheck—fix baseUrl deprecation in tsconfig first.

TypeScript 6.0 introduces breaking changes/deprecations, and with "typescript": "~6.0.3" the web build fails in web/tsconfig.app.json(28,5) with TS5101 (“Option 'baseUrl' is deprecated… Specify 'ignoreDeprecations': '6.0' to silence”). Update web/tsconfig.app.json to migrate away from baseUrl (or add "ignoreDeprecations": "6.0" as an unblocker) so npm run typecheck / make check-web passes.

🤖 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 `@web/package.json` at line 83, The tsconfig currently triggers TS5101 because
"baseUrl" is deprecated under TypeScript 6.0; open the project's
tsconfig.app.json and under "compilerOptions" either remove/migrate the
"baseUrl" usage (replace with explicit "paths" mappings if needed) or add the
temporary unblocker "ignoreDeprecations": "6.0" so the typecheck passes; ensure
you update the "baseUrl" key and/or add "ignoreDeprecations" in the same
"compilerOptions" object to resolve the error.

"ultracite": "^7.1.1",
"vite": "^7.2.4",
"vite-plugin-node-polyfills": "0.24.0"
Expand Down
Loading