Skip to content

chore(deps): update dependency typescript to v6 #83

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

Closed
SamuelIVX wants to merge 1 commit into from
Closed

chore(deps): update dependency typescript to v6 #83

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 @@ -35,7 +35,7 @@
"eslint-config-next": "16.1.6",
"eslint-plugin-react": "^7.37.5",
"tailwindcss": "^4.1.18",
"typescript": "^5"
"typescript": "^6.0.0"
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Mar 24, 2026

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 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:

🌐 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:

🌐 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:

🏁 Script executed:

cd /dev/null && pwd
git ls-files | grep -i tsconfig

Repository: SamuelIVX/Deltabase

Length of output: 143

🏁 Script executed:

cat -n tsconfig.json

Repository: SamuelIVX/Deltabase

Length of output: 853

🏁 Script executed:

cat -n package.json | head -60

Repository: 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.

},
"engines": {
"node": ">=21.0.0"
Expand Down
Loading