docs: Instant Navigations migration plan and agent DX groundwork - #161
Draft
mkayander wants to merge 5 commits into
Draft
docs: Instant Navigations migration plan and agent DX groundwork#161mkayander wants to merge 5 commits into
mkayander wants to merge 5 commits into
Conversation
- next 16.2.6 → 16.2.12 - react / react-dom 19.2.6 → 19.2.8 - next-auth 4.24.14 → 4.24.15 - @trpc/* 11.17.0 → 11.18.0 - @tanstack/react-query 5.100.11 → 5.101.4 - @next/eslint-plugin-next, @types/react, @types/react-dom
- next 16.2.12 → 16.3.0 - @next/eslint-plugin-next 16.2.12 → 16.3.0 - pnpm minimumReleaseAgeExclude entries for fresh 16.3 packages - next-env.d.ts route type paths updated by Next 16.3
Prisma: - prisma, @prisma/client, @prisma/adapter-pg 7.8.0 → 7.9.1 UI & runtime: - @mui/material, @mui/icons-material 9.0.1 → 9.2.0 - @mui/lab 9.0.0-beta.3 → 9.0.0-beta.6 - @mui/x-charts 9.3.0 → 9.10.1 - @react-three/fiber 9.6.1 → 9.7.0 - three 0.183.2 → 0.185.1, @types/three 0.173.0 → 0.185.3 - axios 1.16.1 → 1.19.0, sharp 0.34.5 → 0.35.3 - monaco-editor 0.55.1 → 0.56.0 - react-resizable-panels, react-virtuoso, sanitize-html, joi, etc. Dev tooling: - eslint 10.4.0 → 10.8.0, prettier 3.8.3 → 3.9.6 - typescript-eslint 8.59.4 → 8.66.0, sass, tsx, semantic-release Prettier 3.9 reformatted union types in a few files (no logic changes).
Next.js 16.3.0 + Turbopack + Pages Router i18n breaks Vercel routing: /api/* requests fall through to static /en/404 instead of serverless functions (known adapter issue; i18n-api-support test disabled for Turbopack). 16.2.12 previews work; keep other dependency updates.
- Design doc: App Router requirement, i18n conflict, Vercel 16.3 gate, phased rollout - TODO checklist for phases 0-4 - CLAUDE.md imports AGENTS.md - AGENTS.md: Instant Nav doc paths and Pages Router guardrail
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a phased plan for adopting Next.js 16.3 Instant Navigations and related agent-native DX in dStruct.
Instant Navigations (
cacheComponents,partialPrefetching,'use cache', Instant Insights) is App Router only. This repo is still Pages Router (src/pages/) with 20-localei18ninnext.config.mjs, so full adoption requires an App Router migration — not a config toggle.What's in this PR
vibe-docs/Instant-Navigations-Design.md— architecture, i18n conflict, Vercel 16.3 gate, phased rollout (marketing pilot → playground shell → deprecate Pages)vibe-docs/Instant-Navigations-TODO.md— checklist per phaseCLAUDE.md—@AGENTS.mdfor Claude CodeAGENTS.md— Instant Nav bundled doc paths + guardrail: do not enablecacheComponentson Pages RouterRecommended next steps (not in this PR)
/api/trpc/*and/api/auth/sessionpreviews/,/privacy,/dailyunderapp/[lang]/with extractedAppProviderscacheComponents+partialPrefetchingonly after first App routes existRelated