c9d9f1131c
* Rename getServerProps to getServerSideProps * Remove unstable_ prefix from new methods * Add error when legacy methods are detected * Add legacy methods for babel transform * Add unstable_getServerSideProps also * Apply suggestions from code review Co-Authored-By: Joe Haddad <joe.haddad@zeit.co> * Update types import Co-authored-by: Joe Haddad <timer150@gmail.com>
2.1 KiB
2.1 KiB
Invalid getStaticPaths Return Value
Why This Error Occurred
In one of the page's getStaticPaths
the return value had the incorrect shape.
Possible Ways to Fix It
Make sure to return the following shape from getStaticPaths
:
export async function 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