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

[docs] Clarify "When does getStaticProps run" note #37289

Merged
merged 3 commits into from
May 29, 2022
Merged

[docs] Clarify "When does getStaticProps run" note #37289

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
715638c
Correct "When does getStaticPaths run" bullets
Clariity May 29, 2022
abebcc3
Add sub-section for getStaticProps
Clariity May 29, 2022
90365f9
Merge branch 'canary' into fix-37288
ijjk May 29, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/basic-features/data-fetching/get-static-paths.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,8 @@ 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/).

### How does getStaticProps run with regards to getStaticPaths

- `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`
Expand Down