#4124: Fixed initial Nuxt 3 SSR builder render issue by passing route… #4125
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.
The Nuxt 3 and Nuxt 3 catch all solutions (here and here) do not work out of the box for SSR because preview query parameters are not passed to isPreviewing().
To reproduce:
Implement one of the Nuxt 3 examples above in an SSR Nuxt 3 app.
Attempt to access a page through the builder.io preview environment
Result: It'll say "Content not found" or you'll get the error pop-up that something is not configured correctly.
Fun note: If you update your app locally, HMR triggers a client update which then DOES trigger a working client call with fetchOneEntry - enabling the preview environment to work. The initial impression is a flaky builder preview environment that sometimes works and sometimes does not (no good!).