49d5e362d4
Lands #37431 again, but it only solves the re-render issue completely for the middleware case (closes #38267), not the `rewrites` case (#37139). For `rewrites`, the blocker is `isReady` always being `false` initially and to match the markup on hydration we can't simply work around it without a re-render. Need to come up with another fix. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples) |
||
---|---|---|
.. | ||
add-locale.ts | ||
add-path-prefix.ts | ||
add-path-suffix.ts | ||
app-paths.ts | ||
compare-states.ts | ||
escape-path-delimiters.ts | ||
format-next-pathname-info.ts | ||
format-url.ts | ||
get-asset-path-from-route.ts | ||
get-next-pathname-info.ts | ||
get-route-from-asset-path.ts | ||
index.ts | ||
is-dynamic.ts | ||
parse-path.ts | ||
parse-relative-url.ts | ||
parse-url.ts | ||
path-has-prefix.ts | ||
path-match.ts | ||
prepare-destination.ts | ||
querystring.ts | ||
relativize-url.ts | ||
remove-path-prefix.ts | ||
remove-trailing-slash.ts | ||
resolve-rewrites.ts | ||
route-matcher.ts | ||
route-regex.ts | ||
sorted-routes.ts |