02103feb29
This serves to address a few problems as it relates to headers handling within the App Page render pipeline. 1. During static generation, we should not write to the response directly as the revalidation for static responses is performed out of band from the actual request/response as a stale version can be served early. This is partially addressed by modifying the `onHeaders` to only write when there it is not during static generation, but long term I'd hope to see that we can instead pass a immutable request and `null` for the response to help indicate to the render pipeline that it should instead persist the data into the `RenderResult` objects. Alternatively, the response could use a mocked version that would then supersede the `RenderResult` and be used instead. 2. The types for rendering App Pages were merged incorrectly, so this additionally restructures the way that we initialize those renderers such that only the options that are applicable to each renderer is passed down. |
||
|---|---|---|
| .. | ||
| compiled.d.ts | ||
| global.d.ts | ||
| index.d.ts | ||
| misc.d.ts | ||
| react-dom.d.ts | ||
| react.d.ts | ||
| webpack.d.ts | ||