chore(deps): upgrade to typescript 7

[JeanMeijer]

Description

Briefly describe what you did and why.

Screenshots / Recordings

Add screenshots or recordings here to help reviewers understand your changes.

Type of Change

• Bug fix
• New feature
• Breaking change
• UI/UX update
• Docs update
• Refactor / Cleanup

Related Areas

• Authentication
• Calendar UI
• Data/API
• Docs

Testing

• Manual testing performed
• Cross-browser testing (if UI changes)
• Mobile responsiveness verified (if UI changes)

Checklist

• I’ve read the CONTRIBUTING guide
• My code works and is understandable and follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in complex areas
• I have updated the documentation
• Any dependent changes are merged and published

Notes

(Optional) Add anything else you'd like to share.

By submitting, I confirm I understand and stand behind this code. If AI was used, I’ve reviewed and verified everything myself.

---

Summary by cubic

Upgraded the repo to TypeScript 7 and adopted the Next.js TypeScript CLI for faster, stricter builds. Also bumped Next to 16.3.0-preview.6 and updated generated type imports to the new .next/types paths.

• Dependencies
  • Added @typescript/native and upgraded typescript to ^7.0.2 in apps/web.
  • Overrode next to 16.3.0-preview.6 and bumped eslint-config-next/@next/eslint-plugin-next to match.
  • Enabled experimental.useTypeScriptCli: true in apps/web/next.config.ts.

^{Written for commit b8027ab. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
analog	Ready	Preview, Comment	Jul 16, 2026 6:04pm

[cubic-dev-ai]

2 issues found across 6 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/web/package.json">

<violation number="1" location="apps/web/package.json:152">
P2: The web workspace now exposes TypeScript 7 to tooling that explicitly supports only TypeScript <6.1, and TypeScript 7.0 does not provide the compiler API those ESLint packages use, so lint/Next type tooling can fail or emit unsupported-version errors. The TypeScript 6 compatibility package should remain under the `typescript` name while TypeScript 7 is invoked through the existing `@typescript/native` alias, or all compiler-API consumers should be upgraded to TypeScript 7-compatible releases.</violation>
</file>

<file name="package.json">

<violation number="1" location="package.json:21">
P2: Most workspace type checks will continue running TypeScript 6 despite this TypeScript 7 addition, because `@typescript/native` is a separate, unused dependency while the shared `typescript` catalog remains `^6`. Updating the catalog or wiring this alias into the workspace `type-check` commands would make the upgrade effective.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: The web workspace now exposes TypeScript 7 to tooling that explicitly supports only TypeScript <6.1, and TypeScript 7.0 does not provide the compiler API those ESLint packages use, so lint/Next type tooling can fail or emit unsupported-version errors. The TypeScript 6 compatibility package should remain under the typescript name while TypeScript 7 is invoked through the existing @typescript/native alias, or all compiler-API consumers should be upgraded to TypeScript 7-compatible releases.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/web/package.json, line 152:

<comment>The web workspace now exposes TypeScript 7 to tooling that explicitly supports only TypeScript <6.1, and TypeScript 7.0 does not provide the compiler API those ESLint packages use, so lint/Next type tooling can fail or emit unsupported-version errors. The TypeScript 6 compatibility package should remain under the `typescript` name while TypeScript 7 is invoked through the existing `@typescript/native` alias, or all compiler-API consumers should be upgraded to TypeScript 7-compatible releases.</comment>

<file context>
@@ -147,8 +147,8 @@
+    "eslint-config-next": "16.3.0-preview.6",
     "tailwindcss": "^4.3.0",
-    "typescript": "catalog:"
+    "typescript": "^7.0.2"
   }
 }
</file context>

[cubic-dev-ai]

P2: Most workspace type checks will continue running TypeScript 6 despite this TypeScript 7 addition, because @typescript/native is a separate, unused dependency while the shared typescript catalog remains ^6. Updating the catalog or wiring this alias into the workspace type-check commands would make the upgrade effective.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At package.json, line 21:

<comment>Most workspace type checks will continue running TypeScript 6 despite this TypeScript 7 addition, because `@typescript/native` is a separate, unused dependency while the shared `typescript` catalog remains `^6`. Updating the catalog or wiring this alias into the workspace `type-check` commands would make the upgrade effective.</comment>

<file context>
@@ -18,11 +18,15 @@
     "db:studio": "dotenv -- turbo run db:studio"
   },
   "devDependencies": {
+    "@typescript/native": "npm:typescript@^7.0.2",
     "dotenv-cli": "^11.0.0",
     "oxfmt": "^0.54.0",
</file context>