chore(deps-dev): bump typescript from 5.9.3 to 6.0.3 in /web - #99
chore(deps-dev): bump typescript from 5.9.3 to 6.0.3 in /web#99dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
📝 WalkthroughWalkthroughThe PR updates the TypeScript devDependency in ChangesTypeScript Dependency Upgrade
🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with 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.
Inline comments:
In `@web/package.json`:
- 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.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 5973dd8a-ac84-4b2d-a84c-15cd42b34d5b
⛔ Files ignored due to path filters (1)
web/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
web/package.json
| "@vitejs/plugin-react": "^5.1.1", | ||
| "rollup-plugin-visualizer": "6.0.3", | ||
| "typescript": "~5.9.3", | ||
| "typescript": "~6.0.3", |
There was a problem hiding this comment.
🧩 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:
- 1: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-6-0.html
- 2: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/
- 3: https://truesolvers.com/articles/typescript-60-breaking-changes-what-breaks-and-what-already-helps
- 4: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0-rc/
- 5: https://github.com/microsoft/TypeScript-Website/blob/v2/packages/documentation/copy/en/release-notes/TypeScript%206.0.md
- 6: https://stacknotice.com/blog/typescript-6-breaking-changes-migration-guide
🏁 Script executed:
#!/bin/bash
# Description: Run typecheck with TypeScript 6.0.3 to verify compatibility
cd web && npm install && npm run typecheckRepository: 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.
Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.9.3 to 6.0.3. - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Commits](microsoft/TypeScript@v5.9.3...v6.0.3) --- updated-dependencies: - dependency-name: typescript dependency-version: 6.0.3 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
bdde1d6 to
4b72dd8
Compare
There was a problem hiding this comment.
♻️ Duplicate comments (1)
web/package.json (1)
83-83:⚠️ Potential issue | 🔴 Critical | ⚡ Quick winTypeScript 6.0 upgrade blocked by deprecated
baseUrlin tsconfig.The past review identified that TypeScript 6.0 deprecates
baseUrl, causing TS5101 error. Theweb/tsconfig.jsonstill contains"baseUrl": ".", sonpm run typecheck(used bymake check-web) will fail. Fix the tsconfig before merging this bump:
- Recommended: Migrate away from
baseUrl- the existingpathsmappings can reference explicit locations- Temporary unblocker: Add
"ignoreDeprecations": "6.0"tocompilerOptions(but this must be removed before TS 7.0)🤖 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 uses the deprecated "baseUrl" compiler option which breaks TypeScript 6.0; update the project's tsconfig.json by removing "baseUrl" and adjusting any "paths" entries to use explicit relative paths (or absolute package references) so imports still resolve, or as a temporary unblocker add "ignoreDeprecations": "6.0" under "compilerOptions" to suppress the TS5101 deprecation until you fully migrate; ensure the change lets `npm run typecheck` (used by `make check-web`) succeed and remove the temporary "ignoreDeprecations" before upgrading to TS 7.0.
🤖 Prompt for all review comments with 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.
Duplicate comments:
In `@web/package.json`:
- Line 83: The tsconfig currently uses the deprecated "baseUrl" compiler option
which breaks TypeScript 6.0; update the project's tsconfig.json by removing
"baseUrl" and adjusting any "paths" entries to use explicit relative paths (or
absolute package references) so imports still resolve, or as a temporary
unblocker add "ignoreDeprecations": "6.0" under "compilerOptions" to suppress
the TS5101 deprecation until you fully migrate; ensure the change lets `npm run
typecheck` (used by `make check-web`) succeed and remove the temporary
"ignoreDeprecations" before upgrading to TS 7.0.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 93baca6d-0e75-4b0c-ac3c-32e08cfbee0d
⛔ Files ignored due to path filters (1)
web/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
web/package.json
|
Deferring the TypeScript 5.9 → 6.0 major bump. TS 6.0 deprecates |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
1 participant
Bumps typescript from 5.9.3 to 6.0.3.
Release notes
Sourced from typescript's releases.
Commits
050880cBump version to 6.0.3 and LKGeeae9dd🤖 Pick PR #63401 (Also check package name validity in...) into release-6.0 (#...ad1c695🤖 Pick PR #63368 (Harden ATA package name filtering) into release-6.0 (#63372)0725fb4🤖 Pick PR #63310 (Mark class property initializers as...) into release-6.0 (#...607a22aBump version to 6.0.2 and LKG9e72ab7🤖 Pick PR #63239 (Fix missing lib files in reused pro...) into release-6.0 (#...35ff23d🤖 Pick PR #63163 (Port anyFunctionType subtype fix an...) into release-6.0 (#...e175b69Bump version to 6.0.1-rc and LKGaf4caacUpdate LKG8efd7e8Merge remote-tracking branch 'origin/main' into release-6.0Summary by CodeRabbit