getStaticProps

    Exporting a function called getStaticProps will pre-render a page at build time using the props returned from the function:

    You can import modules in top-level scope for use in getStaticProps. Imports used will not be bundled for the client-side. This means you can write server-side code directly in getStaticProps, including fetching data from your database.

    The context parameter is an object containing the following keys:

    • params contains the route parameters for pages using . For example, if the page name is [id].js , then params will look like { id: ... }. You should use this together with getStaticPaths, which we’ll explain later.
    • preview is true if the page is in the Preview Mode and undefined otherwise.
    • previewData contains the data set by setPreviewData.
    • locale contains the active locale (if enabled).
    • locales contains all supported locales (if enabled).
    • defaultLocale contains the configured default locale (if enabled).

    The getStaticProps function should return an object containing either props, redirect, or notFound followed by an optional revalidate property.

    The props object is a key-value pair, where each value is received by the page component. It should be a serializable object so that any props passed, could be serialized with .

    1. export async function getStaticProps(context) {
    2.   return {
    3.     props: { message: `Next.js is awesome` }, // will be passed to the page component as props
    4.   }
    5. }

    The revalidate property is the amount in seconds after which a page re-generation can occur (defaults to false or no revalidation).

    The cache status of a page leveraging ISR can be determined by reading the value of the x-nextjs-cache response header. The possible values are the following:

    • MISS - the path is not in the cache (occurs at most once, on the first visit)
    • STALE - the path is in the cache but exceeded the revalidate time so it will be updated in the background
    • HIT - the path is in the cache and has not exceeded the revalidate time

    The notFound boolean allows the page to return a 404 status and 404 Page. With notFound: true, the page will return a 404 even if there was a successfully generated page before. This is meant to support use cases like user-generated content getting removed by its author. Note, follows the same revalidate behavior .

    1. export async function getStaticProps(context) {
    2.   const res = await fetch(`https://.../data`)
    3.   const data = await res.json()
    5.   if (!data) {
    6.     return {
    7.       notFound: true,
    8.     }
    9.   }
    11.   return {
    12.   }
    13. }

    The redirect object allows redirecting to internal or external resources. It should match the shape of { destination: string, permanent: boolean }.

    In some rare cases, you might need to assign a custom status code for older HTTP clients to properly redirect. In these cases, you can use the statusCode property instead of the permanent property, but not both. You can also set basePath: false similar to redirects in next.config.js.

    If the redirects are known at build-time, they should be added in instead.

    In order to do so you have to get the full path to a file.

    Since Next.js compiles your code into a separate directory you can’t use __dirname as the path it will return will be different from the pages directory.

    Instead you can use process.cwd() which gives you the directory where Next.js is being executed.

    1. import { promises as fs } from 'fs'
    2. import path from 'path'
    4. // posts will be populated at build time by getStaticProps()
    5. function Blog({ posts }) {
    6.   return (
    7.     <ul>
    8.       {posts.map((post) => (
    9.         <li>
    10.           <h3>{post.filename}</h3>
    11.           <p>{post.content}</p>
    12.         </li>
    13.       ))}
    14.     </ul>
    15.   )
    16. }
    18. // This function gets called at build time on server-side.
    19. // It won't be called on client-side, so you can even do
    20. // direct database queries.
    21. export async function getStaticProps() {
    22.   const postsDirectory = path.join(process.cwd(), 'posts')
    25.   const posts = filenames.map(async (filename) => {
    26.     const filePath = path.join(postsDirectory, filename)
    27.     const fileContents = await fs.readFile(filePath, 'utf8')
    29.     // Generally you would parse/transform the contents
    30.     // For example you can transform markdown to HTML here
    32.     return {
    33.       content: fileContents,
    34.     }
    35.   })
    36.   // By returning { props: { posts } }, the Blog component
    37.   // will receive `posts` as a prop at build time
    38.   return {
    39.     props: {
    40.       posts: await Promise.all(posts),
    41.     },
    42.   }
    43. }
    45. export default Blog

    You can use the GetStaticProps type from next to type the function:

    If you want to get inferred typings for your props, you can use InferGetStaticPropsType<typeof getStaticProps>:

    1. import { InferGetStaticPropsType } from 'next'
    3. type Post = {
    4.   author: string
    5.   content: string
    6. }
    8. export const getStaticProps = async () => {
    9.   const res = await fetch('https://.../posts')
    10.   const posts: Post[] = await res.json()
    12.   return {
    13.     props: {
    14.       posts,
    15.     },
    16.   }
    17. }
    19. function Blog({ posts }: InferGetStaticPropsType<typeof getStaticProps>) {
    20.   // will resolve posts to type Post[]
    21. }
    22. export default Blog

    For more information on what to do next, we recommend the following sections: