Change fallback false to blocking to avoid 404 error when trying to revalidate a new article #213
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.
Based on:
#212
Fallback set to
false
messes up with the incremental static generation when a new article is created. That is due to Next.js trying to revalidate a page that is not generated, which returns 404 and aborts the revalidation process.Fallback
false
only generates pages during build time. Fallbackblocking
generates pages at build time, and when it exists in the CMS, but has not been yet generated, during a first request to that page, the page gets generated.