Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change getStaticProps to getStaticPaths in getStaticPaths docs #36403

Merged
merged 1 commit into from Apr 23, 2022
Merged

Change getStaticProps to getStaticPaths in getStaticPaths docs #36403

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/basic-features/data-fetching/get-static-paths.md
View file
Open in desktop
Expand Up @@ -37,9 +37,9 @@ You should use `getStaticPaths` if you’re statically pre-rendering pages that

`getStaticPaths` will only run during build in production, it will not be called during runtime. You can validate code written inside `getStaticPaths` is removed from the client-side bundle [with this tool](https://next-code-elimination.vercel.app/).

- `getStaticProps` runs during `next build` for any `paths` returned during build
- `getStaticProps` runs in the background when using `fallback: true`
- `getStaticProps` is called before initial render when using `fallback: blocking`
- `getStaticPaths` runs during `next build` for any `paths` returned during build
- `getStaticPaths` runs in the background when using `fallback: true`
- `getStaticPaths` is called before initial render when using `fallback: blocking`

## Where can I use getStaticPaths

Expand Down