rsnext/packages
Gerald Monaco ade52553b6
Add RequestContext (#27303)
How a page is rendered depends on whether or not we're streaming. For example, if we're just rendering to a `string` or we're generating a response for a crawler or other robot, we don't want React 18 to dynamically flush `<script>` tags to update Suspense boundaries as they resolve. Instead, we just want to wait for the full HTML to resolve and return a result similar to `renderToString`.

This is what `RequestContext` and the new/refactored `pipe` and `getStaticHTML` methods allow.  They add a `requireStaticHTML` option that gets passed down. A follow-up PR will make sure this is `true` when serving a robot, and also ensure React is invoked appropriately.
2021-07-20 16:04:31 +00:00
..
create-next-app v11.0.2-canary.17 2021-07-19 18:31:57 -05:00
eslint-config-next v11.0.2-canary.17 2021-07-19 18:31:57 -05:00
eslint-plugin-next v11.0.2-canary.17 2021-07-19 18:31:57 -05:00
next Add RequestContext (#27303) 2021-07-20 16:04:31 +00:00
next-bundle-analyzer v11.0.2-canary.17 2021-07-19 18:31:57 -05:00
next-codemod v11.0.2-canary.17 2021-07-19 18:31:57 -05:00
next-env v11.0.2-canary.17 2021-07-19 18:31:57 -05:00
next-mdx v11.0.2-canary.17 2021-07-19 18:31:57 -05:00
next-plugin-storybook v11.0.2-canary.17 2021-07-19 18:31:57 -05:00
next-polyfill-module v11.0.2-canary.17 2021-07-19 18:31:57 -05:00
next-polyfill-nomodule v11.0.2-canary.17 2021-07-19 18:31:57 -05:00
react-dev-overlay v11.0.2-canary.17 2021-07-19 18:31:57 -05:00
react-refresh-utils v11.0.2-canary.17 2021-07-19 18:31:57 -05:00