Skip to content

Bump typescript from 5.4.5 to 6.0.3 #25

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

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump typescript from 5.4.5 to 6.0.3 #25

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
28 changes: 15 additions & 13 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 web/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,6 @@
"@types/node": "20.11.17",
"@types/react": "18.3.3",
"@types/react-dom": "18.3.0",
"typescript": "5.4.5"
"typescript": "6.0.3"

@coderabbitai coderabbitai Bot May 23, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🌐 Web query:

Does TypeScript 6.0.3 exist and what are the breaking changes in TypeScript 6.0?

💡 Result:

Yes—TypeScript 6.0.3 exists. It’s published as release tag v6.0.3 in the microsoft/TypeScript repository, with a release date of 2026-04-16. [1] Breaking changes in TypeScript 6.0 (not 6.0.3 patch): 1) Transition/compat goals: TypeScript 6.0 is a bridge toward TypeScript 7.0 (native port) and introduces breaking changes and deprecations intended to be resolved before 7.0. [2][3] 2) New default deprecations behavior via tsconfig: The release notes explain that TypeScript 6.0 deprecations can be ignored by setting "ignoreDeprecations": "6.0" in tsconfig, but TypeScript 7.0 will not support any of these deprecated options. [2][3] 3) strict is now true by default: The TypeScript 6.0 RC announcement states that strict is now true by default. If you previously relied on the default false, you must explicitly set "strict": false. [4] 4) types now defaults to []: The RC announcement notes that "types" now defaults to an empty array ([]). [4] 5) Deprecations of several compiler options in 6.0: The RC announcement lists deprecated options including target: es5, moduleResolution node (node10), moduleResolution classic, --alwaysStrict false, outFile, and others (as shown in its “Deprecated:” sections). [4] If you want, paste your tsconfig.json and I’ll map which of the above are likely to affect your project specifically.

Citations:

🌐 Web query:

Is Next.js 16.2.6 compatible with TypeScript 6.0.3?

💡 Result:

Not fully guaranteed: Next.js 16.2.6 requires a minimum TypeScript version of 5.1.0, so TypeScript 6.0.3 should be compatible based on the minimum-version requirement. However, Next.js does not explicitly state compatibility with specific newer TypeScript patch versions (like 6.0.3) in the official docs—only that you must use at least 5.1.0. [1][2] Evidence from the official Next.js docs: - Next.js “Minimum TypeScript version: v5.1.0” in its installation/TypeScript guidance. [2] - The Next.js TypeScript configuration docs also describe TypeScript support and note errors with older TypeScript, recommending upgrading to the latest. [3] Conclusion: - Since 6.0.3 is greater than the stated minimum 5.1.0, it is expected to work with Next.js 16.2.6. [2] - If you hit any build/typecheck issues, the official guidance is to update TypeScript and related types (e.g., @types/react) to latest compatible versions. [3]

Citations:

🏁 Script executed:

#!/bin/bash
# Verify that package-lock.json contains TypeScript 6.0.3

echo "Checking package-lock.json for TypeScript version..."
if [ -f "web/package-lock.json" ]; then
  jq -r '.packages."node_modules/typescript".version // .dependencies.typescript.version // "NOT FOUND"' web/package-lock.json
else
  echo "package-lock.json not found in web directory"
fi

echo -e "\nChecking for TypeScript configuration files..."
fd -e json tsconfig --type f

Repository: p-to-q/aleph

Length of output: 200

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "=== web/package.json typescript ==="
node -e 'const p=require("./web/package.json"); console.log(p.devDependencies?.typescript ?? p.dependencies?.typescript ?? "MISSING");'

echo -e "\n=== web/package-lock.json typescript resolved ==="
if [ -f "web/package-lock.json" ]; then
  node - <<'NODE'
const fs=require('fs');
const lock=JSON.parse(fs.readFileSync('web/package-lock.json','utf8'));
const v = lock?.packages?.["node_modules/typescript"]?.version
  ?? lock?.dependencies?.typescript?.version
  ?? null;
console.log(v ?? "NOT FOUND");
NODE
fi

echo -e "\n=== tsconfig strict / ignoreDeprecations ==="
for f in web/tsconfig.json tsconfig.base.json; do
  if [ -f "$f" ]; then
    echo -e "\n--- $f ---"
    rg -n '"strict"\s*:' "$f" || true
    rg -n 'ignoreDeprecations' "$f" || true
    rg -n 'compilerOptions' "$f" | head -n 20 || true
  fi
done

Repository: p-to-q/aleph

Length of output: 351

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "=== web/package.json typescript ==="
node -e 'const p=require("./web/package.json"); console.log(p.devDependencies?.typescript ?? p.dependencies?.typescript ?? "MISSING");'

echo -e "\n=== web/package-lock.json typescript resolved ==="
if [ -f "web/package-lock.json" ]; then
  node - <<'NODE'
const fs=require('fs');
const lock=JSON.parse(fs.readFileSync('web/package-lock.json','utf8'));
const v = lock?.packages?.["node_modules/typescript"]?.version
  ?? lock?.dependencies?.typescript?.version
  ?? null;
console.log(v ?? "NOT FOUND");
NODE
fi

echo -e "\n=== tsconfig strict / ignoreDeprecations ==="
for f in web/tsconfig.json tsconfig.base.json; do
  if [ -f "$f" ]; then
    echo -e "\n--- $f ---"
    rg -n '"strict"\s*:' "$f" || true
    rg -n 'ignoreDeprecations' "$f" || true
    rg -n 'compilerOptions' "$f" | head -n 20 || true
  fi
done

Repository: p-to-q/aleph

Length of output: 351

Fix lockfile sync: TypeScript set to 6.0.3 but lockfile still pins 5.4.5

web/package.json updates typescript to 6.0.3, but web/package-lock.json still resolves typescript to 5.4.5, so the upgrade may not actually take effect unless the lockfile is updated in this PR.

Next.js 16.2.6 should work with TS 6.0.3 (Next requires TypeScript >= 5.1.0), but TS 6.0 introduces breaking/deprecation changes—your web/tsconfig.json and tsconfig.base.json already have "strict": true, so focus on deprecated compiler options and run npm ci + npm run build/tsc --noEmit to confirm.

🤖 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 20, The package.json was bumped to TypeScript 6.0.3
but the lockfile still pins 5.4.5; regenerate the lockfile so installs actually
use 6.0.3 by running npm ci (or delete web/package-lock.json and run npm install
in the web folder) to update web/package-lock.json, then run npm run build and
tsc --noEmit to catch compile errors; also review web/tsconfig.json and
web/tsconfig.base.json for deprecated/removed compiler options introduced in TS6
and adjust (or remove) any deprecated flags so the project builds cleanly with
TypeScript 6.0.3.

}
}