Open
Description
This needs further investigation to diagnose the cause of the problem, but seems like there is some weird interaction when both middleware rewrite and next.config.js rewrite are used where Next's client router is not setting router.query
to match expected dynamic segments
Data
The following is parsed automatically by the Next.js repo e2e test report generator.
test: Middleware Rewrite should handle catch-all rewrite correctly, Middleware Rewrite should handle static rewrite from next.config.js correctly, Middleware Rewrite should opt out of prefetch caching for dynamic routes
reason: Middleware rewrites for dynamic routes not setting query/params in router