wip

[mktktmr]

No description provided.

[mktktmr]

Quick take

• The guard keeps working on Next 16, but we still lean on private next/dist/... modules, so we should watch canary builds for churn.

Details reviewed

• App Router interception (src/components/InterceptAppRouterProvider.tsx, src/hooks/useInterceptedAppRouter.ts) still works: AppRouterContext and the AppRouterInstance API in [email protected] remain unchanged.
• Pages Router interception (src/components/InterceptPagesRouterProvider.tsx, src/hooks/useInterceptedPagesRouter.ts) stays compatible; RouterContext and NextRouter expose the same methods.
• Link interception (src/hooks/useInterceptLinkClicks.ts) continues to be required. The Next 16 next/link implementation still drives navigation through the shared router context, so both the wrapped router and the DOM fallback behave as before.
• History augmentation (src/hooks/useInterceptPopState.ts, src/utils/historyAugmentation.tsx) survives the release: HistoryState is still an object we can spread. Adding a null-guard would future-proof us in case Next ever emits null.

Release-note items to keep in mind

• Runtime baseline jumps to Node 20.9 and TypeScript ≥5.1; update CI/example environments accordingly.
• Sync variants of params, searchParams, cookies(), etc., are gone. We don’t call them in the library, but documentation/examples should use the async forms.
• Turbopack becomes the default bundler. No direct impact here, but build tooling/log output will differ.
• next lint command was removed. We already rely on external tooling, so no action needed.

[mktktmr]

Continue on original repo.

LayerXcom#51