47ff1eb95a
* Ability to Disable SSG Fallback * Throw error when value is missing * Fix existing tests * Adjust error message * Do not render fallback at build time for `fallback: false` page * Fix existing fallback behavior * fix build * fix version * fix some tests * Fix last test * Add docs for get static paths * Add explicit mode tests * test for fallback error message
2.1 KiB
2.1 KiB
Invalid unstable_getStaticPaths Return Value
Why This Error Occurred
In one of the page's unstable_getStaticPaths
the return value had the incorrect shape.
Possible Ways to Fix It
Make sure to return the following shape from unstable_getStaticPaths
:
export async function unstable_getStaticPaths() {
return {
paths: Array<string | { params: { [key: string]: string } }>,
fallback: boolean
}
}
There are two required properties:
paths
: this property is an Array of URLs ("paths") that should be statically generated at build-time. The returned paths must match the dynamic route shape.fallback
: this property is a Boolean, specifying whether or not a fallback version of this page should be generated.- Enabling
fallback
(viatrue
) allows you to return a subset of all the possible paths that should be statically generated. At runtime, Next.js will statically generate the remaining paths the first time they are requested. Consecutive calls to the path will be served as-if it was statically generated at build-time. This reduces build times when dealing with thousands or millions of pages. - Disabling
fallback
(viafalse
) requires you return the full collection of paths you would like to statically generate at build-time. At runtime, any path that was not generated at build-time will 404.
- Enabling