Content
@
0 reply
0 recast
0 reaction
matt
@matthewmorek
2 replies
1 recast
16 reactions
Darryl Yeo 🛠️
@darrylyeo
https://warpcast.com/dwr.eth/0xf8fa53c1
1 reply
0 recast
1 reaction
matt
@matthewmorek
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
1 reply
0 recast
3 reactions
