5 ways to opt out of static rendering in NextJs

In this video, we'll examine dynamic rendering and five ways to disable the default static rendering in NextJs.

👉🏼 The Ultimate NextJs 14 Course

👉🏼 Work with me

Chapters
0:00 Intro
0:48 Project overview
3:09 Fetch options
4:35 Route config options
6:28 Dynamic functions
7:35 noStore function
9:26 searchParams object
10:05 Recap

[andremazetto]

that's crazy - during dev it refreshes and then we move to prod thinking all is well and it static dates etc. Thanks for bringing that up

[nicolaiv.]

Amazing as always. Maybe you could talk more about the specific use cases of Server Actions now that people are more used to them?

[saulgodman]

I like your Videos! I wish u a bunch of new followers :)

Best from Germany

[govindkarthikeyan]

Every content talked about dynamic rendering in server components. All these different opt-out options are valid for client components as well ? I am sure cookie() headers() and searchParams options are only specific to server components. Can you expand this discussion to client components 🙏

[Luisllaboj]

Until now I think you actually need to wrap your dynamic components in a suspense boundary in case you use dynamic functions (noStore()) or request-time features (searchParams) so it will keeo your route static while only making the component dynamic. noStore() isnt that granular as it is for now until Partial Prerendering it's a standard and you wrap components in suspense.

[kamill]

I think you missed the revalidate tag functionality, wich is i my opinion crucial to ISR

[codechange]

Why why are you not make video on next node full functionality because I want to learn it and i said many time in chat