Skip to content

chore: upgrade TypeScript to v7 - #385

Merged
PinJinx merged 2 commits into
AOSSIE-Org:mainfrom
RounakKumarAgarwal:feat/typescript-7
Aug 18, 2026
Merged

chore: upgrade TypeScript to v7#385
PinJinx merged 2 commits into
AOSSIE-Org:mainfrom
RounakKumarAgarwal:feat/typescript-7

Conversation

@RounakKumarAgarwal

@RounakKumarAgarwal RounakKumarAgarwal commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Closes #381

What

Bumps typescript from ^5.7.2 to ^7.0.0.

Why

TS 7.0 (native Go compiler, "Project Corsa") went GA on July 8, 2026 with
typically 8-12x faster full builds. It's a faithful port, not a redesign —
type-checking semantics match 6.0.

Risk assessment for this repo

  • tsconfig.json uses moduleResolution: bundler + noEmit: true — Vite
    does actual transpilation, tsc is type-check only.
  • Lint/format is Biome (Rust toolchain), not ESLint/@typescript-eslint, so
    there's no typed-lint plugin depending on the TS compiler API.
  • TS 7.0 lacks a stable programmatic compiler API until 7.1 (~Oct 2026), but
    nothing in this stack calls into that API directly, so it doesn't apply here.

Verification

  • npx tsc --noEmit — passes, zero errors
  • npm run build (Vite + Nitro) — passes
  • npm run check (Biome) — 56 pre-existing errors, confirmed unrelated by
    comparing against TS 5.7.2 via git stash
  • npm test (Vitest) — no test files exist in the repo currently
    (confirmed pre-existing, unrelated to this change)

Scoped narrowly to the TS version bump only — did not touch the pre-existing
Biome errors or missing tests, to keep this reviewable and separate from the
broader dependency cleanup in #362.

Summary by CodeRabbit

  • Chores
    • Updated the TypeScript development tooling to a newer version.

- Bump typescript from ^5.7.2 to ^7.0.0
- TS 7.0 is a native Go port (Project Corsa), GA July 8 2026;
  type-checking semantics are unchanged from 6.0
- Verified: tsc --noEmit passes with zero errors, npm run build
  (Vite + Nitro) succeeds
- Biome lint errors (56, pre-existing) and missing test files were
  confirmed unrelated to this change via git stash comparison
  against the prior TS version
- No programmatic-compiler-API dependents in this stack (Vite uses
  bundler mode with noEmit:true; Biome is a separate Rust toolchain),
  so the 7.1 API gap does not apply here

Closes AOSSIE-Org#381
@coderabbitai

coderabbitai Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: da498a7f-2083-4d2a-975f-8390f4c6adeb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 8b34b2e3-576c-40df-bad8-6b75b6807ae1

📥 Commits

Reviewing files that changed from the base of the PR and between 8e44c00 and 5f40b03.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review.


Walkthrough

The pull request updates the TypeScript development dependency in package.json from ^5.7.2 to ^7.0.2.

Changes

TypeScript Upgrade

Layer / File(s) Summary
Update TypeScript dependency
package.json
The TypeScript development dependency changes from ^5.7.2 to ^7.0.2.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 5f40b

This localized TypeScript upgrade reports passing type-check and build checks with no actionable merge-blocking risk remaining beyond normal review.

Possibly related PRs

Suggested reviewers: pinjinx

Poem

A rabbit hops through TypeScript seven,
With fresher tools from cloud to heaven.
One line changed, the path is clear,
New compiler footsteps draw near.
Nibble, build, and cheer!

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the primary change: upgrading the TypeScript dependency to version 7.
Description check ✅ Passed The description identifies issue #381, explains the change and rationale, and records risk assessment and verification results.
Linked Issues check ✅ Passed The package.json change upgrades TypeScript to version 7 and directly addresses the migration requested by issue #381.
Out of Scope Changes check ✅ Passed The only reviewed change is the TypeScript dependency upgrade, which matches issue #381 and the stated narrow scope.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@socket-security

socket-security Bot commented Aug 16, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​tanstack/​router-plugin@​1.168.30 ⏵ 1.168.31991007898 +1100
Updatednitro-nightly@​3.0.1-20260810-113911-16ff2809 ⏵ 3.0.1-alpha.279 -1810082 +196 +1100
Updated@​tanstack/​react-router@​1.170.27 ⏵ 1.170.289210087 +198 +1100
Updated@​tanstack/​react-start@​1.168.44 ⏵ 1.168.4599 +11008898 +1100
Addedtypescript@​7.0.29910089100100

View full report

@gitcordapp

gitcordapp Bot commented Aug 16, 2026

Copy link
Copy Markdown

Link your account with Gitcord

Thanks for opening this PR, @RounakKumarAgarwal!

To receive Discord notifications and contributor tracking for this organization:

  1. Join Discord: https://discord.gg/hjUhu33uAn
  2. In Discord, run /link RounakKumarAgarwal
  3. Paste the verification code into your GitHub bio (or a public gist)
  4. Click Verify in Discord (or run /verify-link RounakKumarAgarwal)

Once linked, Gitcord can notify you about reviews, merges, and more.

Posted by Gitcord

@RounakKumarAgarwal

Copy link
Copy Markdown
Contributor Author

Hi, I received the Gitcord bot message asking me to join the AOSSIE Discord and verify my GitHub account. However, I'm currently unable to join the Discord because my account isn't recognized as a verified contributor yet. Could someone please help me get verified or let me know how I should proceed with the Gitcord linking process?

@Zahnentferner

Copy link
Copy Markdown

@RounakKumarAgarwal , could you share a screenshot of the error you get when you try to join https://discord.gg/hjUhu33uAn ?

@RounakKumarAgarwal

Copy link
Copy Markdown
Contributor Author
image @Zahnentferner

@PinJinx

PinJinx commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

@RounakKumarAgarwal Just remove the node modules and package-lock then use npm install again to fix windows build error. ping me once done

@RounakKumarAgarwal

Copy link
Copy Markdown
Contributor Author

@PinJinx yeah bro let me know what to do ?

@PinJinx

PinJinx commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Exactly what I have said in above message it will fix itself it's usually due to package-lock mismatch

@RounakKumarAgarwal

Copy link
Copy Markdown
Contributor Author

I'm doing wait

Delete node_modules and package-lock.json and reinstall fresh, per
maintainer request (@PinJinx), to resolve the Windows CI failure
where npm ci reported missing lru-cache/typescript entries.

Also picks up transitive dependency drift in the Oxc/Rolldown
toolchain used by Vite (unrelated to TypeScript itself). Verified
tsc --noEmit and npm run build both still pass cleanly.
@RounakKumarAgarwal

Copy link
Copy Markdown
Contributor Author

Done @PinJinx

@PinJinx
PinJinx merged commit 37d898b into AOSSIE-Org:main Aug 18, 2026
8 checks passed
@PinJinx

PinJinx commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Merged, Thanks for the contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Switch to TS 7.

3 participants