feat(vite-plugin-nitro): support static server side data fetching during prerendering #1771
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Closes #1762
What is the new behavior?
When using Server-Side Data Fetching, the data is cached and reused using transfer state only on the first request. To prerender the server-side data fetched along with the route, set the
staticData
flag totrue
in the config object for the prerendered route.For example, a route defined as
src/app/pages/shipping.page.ts
with an associatedsrc/app/pages/shipping.server.ts
has the route and server data prerendered to be completely static.Does this PR introduce a breaking change?
Other information
[optional] What gif best describes this PR or how it makes you feel?