Files
next.js/test/e2e/app-dir/basepath-fallback-params/basepath-fallback-params.test.ts
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

22 lines
620 B
TypeScript

import { nextTestSetup } from 'e2e-utils'
describe('basepath-fallback-params', () => {
const { next } = nextTestSetup({
files: __dirname,
})
it('reads fallback params on a direct visit', async () => {
const browser = await next.browser('/dashboard/items/expected-id')
expect(await browser.elementById('item-id').text()).toBe('expected-id')
})
it('reads fallback params after a client navigation', async () => {
const browser = await next.browser('/dashboard')
await browser.elementByCss('a').click()
expect(await browser.elementById('item-id').text()).toBe('expected-id')
})
})