umi-ssr-issue-prop-pollution

This repo reproduces and verifies SSR server side prop pollution issues.

Forked from umi-ssr-example-normal

Also available on CodeSandbox

Development

run yarn install

$ yarn dev

(if doesn't work, run yarn start then yarn build manually, or just open the CodeSandbox link above)

Production

$ yarn start

How to reproduce the issues:

• Run the project

issue 1:

Stale initProps from server pollutes dynamic routes

• Go to subroute 001 page
• Switch between subroute 002 and 001, page content loads correctly after client-side getInitProps
• Refresh the page at one subroute
• Switch between subroute 002 and 001, page content flashbacks to server-provided stale props before correct prop renders.
• Notice the "isServer" flag on the page and console, which indicates the prop we're using comes from the server getInitProps or not.

Issue 2:

Navigating between page anchors trigger unexpected getInitProps

• Go to "Page with hash"
• Click "#" anchors ahead of paragraphs
• Unexpected getInitProps called, logged in the console
• Issue 1 above may also appear