This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
[✨] How to use both ssg and ssr for the same route #31
Labels
[STAGE-2] incomplete implementation
Remove this label when implementation is complete
[STAGE-2] not fully covered by tests yet
Remove this label when tests are verified to cover the implementation
[STAGE-2] unresolved discussions left
Remove this label when all critical discussions are resolved on the issue
[STAGE-3] docs changes not added yet
Remove this label when the necessary documentation for the feature / change is added
[STAGE-3] missing 2 reviews for RFC PRs
Remove this label when at least 2 core team members reviewed and approved the RFC implementation
Is your feature request related to a problem?
I have a dynamic path in my app,
/search/[query]/index.tsx
. I wanted to optimize it by using ssg for some popular search queries like this:But when I search for something that is not generated with ssg, I get a 404 error. I want it to fallback to the normal path (
/search/[query]/index.tsx
) and get the data from the server as I've defined it there.Describe the solution you'd like
An option to fallback to ssr for not ssg generated paths would be helpful.
Describe alternatives you've considered
Not using ssg.
Additional context
No response
The text was updated successfully, but these errors were encountered: