Files
Tim NeutkensandGitHub 2802106d29 Fix basePath fallback parameter parsing (#95966)
## Summary

- Strip the configured `basePath` from response URL pathnames before
reconstructing fallback route parameters on the client.
- Add production regression coverage for both direct hydration and
client navigation with Cache Components enabled.

This prevents dynamic parameters from shifting when the response URL
includes a base path but the App Router tree does not.

## Verification

- Added production Turbopack E2E coverage for direct visits and client
navigation.

<!-- NEXT_JS_LLM_PR -->
2026-07-22 12:38:29 +02:00

10 lines
148 B
JavaScript

/**
* @type {import('next').NextConfig}
*/
const nextConfig = {
basePath: '/dashboard',
cacheComponents: true,
}
module.exports = nextConfig