chore(deps): update dependency typescript to v6#83
Conversation
📝 WalkthroughWalkthroughThe TypeScript devDependency version range was updated from Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
![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 the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Line 38: TypeScript 6.0 changes the default "types" resolution which can break
builds; update your tsconfig.json by adding an explicit compilerOptions.types
entry to include the needed `@types` packages (for example add "types":
["node","react","react-dom"]) so that Node/React type definitions are picked up;
locate and update the tsconfig.json's compilerOptions section (referencing the
"compilerOptions" object) to add the types array and commit the change.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: c3953787-7113-4307-bfe4-4e99eeb1f9a9
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Lint Code Base
| "eslint-plugin-react": "^7.37.5", | ||
| "tailwindcss": "^4.1.18", | ||
| "typescript": "^5" | ||
| "typescript": "^6.0.0" |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
TypeScript 6.0 breaking changes and migration guide
💡 Result:
TypeScript 6.0, released on March 17, 2026 (final), is a transition release preparing for TypeScript 7.0, a native Go port of the compiler. It introduces new defaults, deprecations (to be removed in 7.0), and some new features. Most changes align with modern JS ecosystem practices. Key Breaking Changes and New Defaults: - strict now defaults to true (previously false). - target defaults to es2025 (previously ES3). - module defaults to es2022 (resolved from target). - rootDir defaults to the tsconfig.json directory (previously inferred from input files) - set to "./src" if needed. - types defaults to none (previously auto-included all @types/*) - explicitly add e.g. "types": ["node"]. - No auto-discovery of @types in node_modules. Deprecations (silence with "ignoreDeprecations": "6.0" in compilerOptions; won't work in 7.0): - baseUrl (no longer needed with paths; use ts5to6 tool to migrate). - module: amd, umd (use bundlers). - import ... asserts { ... } (use with instead). - /// directive removed. - Running tsc with file args when tsconfig.json exists now errors (use tsc -p .). Other Behavioral Changes: - Type ordering in .d.ts output may differ (use --stableTypeOrdering for 6.0-7.0 comparison). - Improved type inference for methods without this. - Subpath imports (#/... syntax) supported. - es2025 lib/target added. - dom lib now includes dom.iterable. Migration Guide: 1. Update to typescript@latest via npm. 2. Run ts5to6 tool (npx ts5to6) for baseUrl/rootDir fixes. 3. Add explicit "types": ["node"] and "rootDir": "./src". 4. Set "ignoreDeprecations": "6.0" temporarily if needed. 5. Review deprecation warnings and update tsconfig. 6. Test build; use --stableTypeOrdering if comparing to 7.0 previews. Official resources: TypeScript blog posts (beta/RC/announce), GitHub issue #62508 (migration guide), #54500 (deprecation tracking). Comprehensive community guide at privatenumber's gist.
Citations:
- 1: https://gist.github.com/privatenumber/3d2e80da28f84ee30b77d53e1693378f
- 2: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/
- 3: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0-beta
- 4: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0-rc/
- 5: 6.0 Migration Guide microsoft/TypeScript#62508
🌐 Web query:
Next.js 16 TypeScript 6.0 compatibility
💡 Result:
Next.js 16 is compatible with TypeScript 6.0. Official Next.js 16 documentation specifies a minimum TypeScript version of 5.1.0, and there are no reported incompatibilities or issues with TypeScript 6.0 (released around early 2026). TypeScript 6.0 introduces features and deprecations that align with modern JavaScript ecosystems, and Next.js leverages recent TypeScript capabilities like native next.config.ts support and type generation. Users should upgrade @types/react and @types/react-dom to latest versions when using TypeScript with Next.js 16. No breaking changes specific to TS 6.0 were found in Next.js docs, changelogs, or GitHub issues.
Citations:
- 1: https://nextjs.org/docs/app/guides/upgrading/version-16
- 2: https://nextjs.org/docs/pages/api-reference/config/typescript
- 3: https://nextjs.org/blog/next-16
- 4: https://nextjs.org/blog/next-16-beta
- 5: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0-rc/
- 6: https://beta.nextjs.org/docs/configuring/typescript
🌐 Web query:
TypeScript 6.0.2 known issues
💡 Result:
TypeScript 6.0.2 is a patch release published on npm around March 23, 2026, shortly after the TypeScript 6.0 stable release on the same date. No specific changelog or release notes were found for 6.0.2 on GitHub releases or official blogs, suggesting it contains minor bug fixes typical for patch versions. Known issues for TypeScript 6.0 series (including post-release reports applicable to 6.0.2): - API bug in isSourceFileDefaultLibrary returning false negatives on program structure reuse in watch mode (fixed quickly via PR #63239). - Bloomberg-reported issues: key mapping in mapped types causing contextual typing failures (#63225); inference producing different results (#63227); JS emit removing certain comments; API changes removing hasDefaultLib. - Open recent issues include type narrowing problems with generics (#63259), mechanism for package.json resolution, lib.d.ts Promise.then return type errors (#63244), exactOptionalPropertyTypes errors with object spread ternaries, compiler crashes, inference changes, watch mode emit issues with isolatedModules, and interface extension errors (#63218). - Language service (LS) bugs for 6.0 JS implementation are no longer fixed, as focus shifted to 7.0 native (issue #62827); test scenarios in TypeScript Native Nightly extension. TypeScript 6.0 is in maintenance mode, with development focused on 7.0. Report new issues on GitHub. Deprecations and breaking changes in 6.0 (e.g., module resolutions, alwaysStrict false, outFile removal) may surface as "issues" if unaddressed.
Citations:
- 1: https://github.com/microsoft/typescript/releases
- 2: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/
- 3: TypeScript 6 API Bug -
isSourceFileDefaultLibraryfalse negative on program structure reuse microsoft/TypeScript#63228 - 4: https://github.com/microsoft/typescript/issues
- 5: https://www.npmjs.com/package/typescript/v/6.0.0-dev.20250811
- 6: Bloomberg feedback for 6.0 microsoft/TypeScript#63245
- 7: Closing TS 6.0 LS issues microsoft/TypeScript#62827
- 8: https://visualstudiomagazine.com/Articles/2026/03/23/TypeScript-6-0-Ships-as-Final-JavaScript-Based-Release-Clears-Path-for-Go-Native-7-0.aspx
🏁 Script executed:
cd /dev/null && pwd
git ls-files | grep -i tsconfigRepository: SamuelIVX/Deltabase
Length of output: 143
🏁 Script executed:
cat -n tsconfig.jsonRepository: SamuelIVX/Deltabase
Length of output: 853
🏁 Script executed:
cat -n package.json | head -60Repository: SamuelIVX/Deltabase
Length of output: 1429
Add explicit "types" field to tsconfig.json to address TypeScript 6.0 breaking change.
TypeScript 6.0 is compatible with Next.js 16.1.4, but it introduces a breaking change: the "types" field now defaults to none (previously auto-discovered all @types packages). The tsconfig.json must be updated to explicitly include the @types packages in use:
"compilerOptions": {
...
"types": ["node", "react", "react-dom"]
}Without this, the build will fail with type errors for React, Node.js, and other @types packages.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` at line 38, TypeScript 6.0 changes the default "types"
resolution which can break builds; update your tsconfig.json by adding an
explicit compilerOptions.types entry to include the needed `@types` packages (for
example add "types": ["node","react","react-dom"]) so that Node/React type
definitions are picked up; locate and update the tsconfig.json's compilerOptions
section (referencing the "compilerOptions" object) to add the types array and
commit the change.
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
2 participants
This PR contains the following updates:
^5→^6.0.0Release Notes
microsoft/TypeScript (typescript)
v6.0.2: TypeScript 6.0Compare Source
For release notes, check out the release announcement blog post.
Downloads are available on:
Configuration
📅 Schedule: Branch creation - "every weekday" in timezone America/New_York, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
Summary by CodeRabbit