WHY is Next JS cache so CONFUSING??

why is nextjs caching so freaking confusing don't you miss the days of the web where it wasn't common practice to have 7,000 different types of cash turned on by default where if you want to turn off a layer of cash you've got to refer to documentation every time and set a specific flag to a specific value and even then it still fraking cashes stuff you may have experienced this where you're opting out of every single possible cash there is in nextjs you've got everything dialed up to 11 you've invalidated caching for all s using the revalidate path function like a good little web developer but then oh wait what's this surprise [Music] a wild client side router cache appeared and guess what you can't opt out of this now the only way we can get around the client side rout cache is by using plain aner tags instead of nextjs Link components obviously the downside to this is our roots are no longer prefetched and each routs we navigate to to in our app is requested directly from the server rather than any cache if we're navigating to Roots programmatically via use router then we also need to call rout to. refresh afterwards to rquest the page from the server what an absolute ballach

Channel: WebDevEducation

Views: 2,679

Keywords:

Id: pqMRC6mS-fE

Length: 1min 15sec (75 seconds)

Published: Wed Oct 25 2023