/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・23・prev /dydx・x.com/darryl__yeo

in case of Next.js it’s a problem created by its design: hide cache behind cache behind cache and never, ever ever, let the developer be in full control of invalidation, and what little control is left, make it painful

So, you’re a frontend framework that supports server-side rendering? 

Name all the ways cached data gets invalidated.

So, you’re a frontend framework that supports server-side rendering? 

Name all the ways cached data gets invalidated.

https://kit.svelte.dev/docs/load#rerunning-load-functions-when-do-load-functions-rerun

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo