Upgrade TypeScript to 7.0.2 - #406
Conversation
Move every workspace package to TypeScript 7.0.2, including sites/hacklytics2027 (was 5.8.3). No tsconfig or source changes were needed; tsc --noEmit and next build type checking both pass on 7. tooling/eslint stays on TypeScript 6.0.2 on purpose: TS 7 no longer ships the classic JS API, and typescript-eslint (latest 8.70.1) still requires typescript <6.1.0. Every lint config resolves typescript-eslint through @query/eslint-config, so pinning it there keeps lint working while the rest of the repo compiles with TS 7.
Brings every dependency with a same-major update to its latest release, including Next.js 16.3.6 (latest stable), tRPC 11.19, TanStack Query 5.103, drizzle, Tailwind 4.3, React 19.3, eslint 10.11 and typescript-eslint 8.70.1. No source changes needed.
Bump dependencies to latest minor/patch (Next.js 16.3.6)
Dependency ReviewThe following issues were found:
|
|
Visit the preview URL for this PR (updated for commit 53ad700): https://hacklytics2027--pr-406-gmovjftw.web.app (expires Thu, 01 Oct 2026 19:30:01 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: c48ba34db61581e25fe2978355160b5eefe0e83f |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 53ad700. Configure here.
| "prettier-plugin-tailwindcss": "^0.6.8" | ||
| "minimatch": "^10.2.6", | ||
| "prettier": "^3.9.9", | ||
| "prettier-plugin-tailwindcss": "^0.8.1" |
There was a problem hiding this comment.
Prettier Tailwind config path breaks
Medium Severity
The prettier-plugin-tailwindcss bump to 0.8.1 errors on an invalid tailwindConfig path. The shared Prettier config still points tailwindConfig at ../tailwind/web.ts, which is not in the repo, so format can fail and v4 class sorting will not load shared-styles.css.
Reviewed by Cursor Bugbot for commit 53ad700. Configure here.


Stacked PRs, merge in order: 1) TS 7 (#406) → 2) minor bumps (#410) → 3) major bumps (#411) → 4) eslint + React Compiler fixes (#412). GitHub retargets each to
devas the one below merges.What
sites/hacklytics2027(was 5.8.3).tsc --noEmitandnext build's type check both run on TS 7 (confirmednext buildstill fails on a deliberate type error).Why tooling/eslint stays on TS 6.0.2
TS 7 no longer ships the classic JS API, and typescript-eslint (latest 8.70.1) requires
typescript <6.1.0. Every lint config resolves typescript-eslint through@query/eslint-config, so pinning TS 6 there keeps lint working while everything else compiles with TS 7. Unpin once typescript-eslint supports 7.Verification
Verified on this branch:
pnpm typecheck,pnpm lint,pnpm test(828 passing), both sites build.Note
Medium Risk
TypeScript 7 and coordinated runtime bumps (Next, React, Stripe, auth adapter) touch the whole build and payment/auth stack without accompanying source changes, so regressions would show up at typecheck, lint, test, or build time.
Overview
Dependency-only refresh across the monorepo: workspaces compile and typecheck on TypeScript 7.0.2 (including
sites/hacklytics2027, previously on 5.8.3), with no tsconfig or application source edits in this diff.tooling/eslint(@query/eslint-config) intentionally stays on TypeScript 6.0.2 while typescript-eslint is bumped to 8.70.1, so lint keeps working under the current typescript-eslint / TS 7 constraint described in the PR notes.The same pass aligns related stacks: Next 16.3.6, React / react-dom 19.3.0, Tailwind 4.3.3, tRPC 11.19, drizzle-orm 0.45.3, Stripe, turbo, ESLint/Prettier tooling, and smaller bumps in
packages/api,packages/db,packages/auth, and both sites.Reviewed by Cursor Bugbot for commit 53ad700. Bugbot is set up for automated code reviews on this repo. Configure here.