mirror of
https://github.com/hanzoai/next.js.git
synced 2026-09-24 17:00:51 +00:00
Shu DingandGitHub
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)
14 lines
317 B
JavaScript
14 lines
317 B
JavaScript
import { useEffect } from 'react'
|
|
import { useRouter } from 'next/router'
|
|
|
|
export default function Index() {
|
|
const { query } = useRouter()
|
|
|
|
useEffect(() => {
|
|
window.__renders = window.__renders || []
|
|
window.__renders.push(query.foo)
|
|
})
|
|
|
|
return <p>A page should not be rerendered if unnecessary.</p>
|
|
}
|