5be04cf8fd
The _requirement_ to export a `generateStaticParams` to get static cache behavior _after_ build time was _really_ surprising behavior for me, and I think others: * https://github.com/vercel/next.js/issues/62195#issuecomment-1952091312 * https://github.com/vercel/next.js/discussions/57961#discussioncomment-8491488 Potentially this is a bug, and not something that should be fixed with documentation? I don't understand next.js caching enough to make that determination, so instead I'm proposing these changes to docs which might be encountered by folks who are surprised by this cache behavior. One point in favor of this being a bug: The CLI reports that a route is `SSG` enabled in the build output, but doesn't actually cache post-build page renders if this export is missing. @awinogrodzki made a demo repo showing this behavior, as described [here](https://github.com/vercel/next.js/discussions/57961#discussioncomment-7468144). --------- Co-authored-by: Delba de Oliveira <delbabrown@gmail.com> Co-authored-by: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com> Co-authored-by: samcx <sam@vercel.com> |
||
|---|---|---|
| .. | ||
| 01-getting-started | ||
| 02-app | ||
| 03-pages | ||
| 04-architecture | ||
| 05-community | ||
| index.mdx | ||