17 ms·

Very interesting. Another Next victim here. One of my anecdotes is the bonkers caching / fetch deduplication. Yes, set cache: no-store. But that only works for

Very interesting. Another Next victim here. One of my anecdotes is the bonkers caching / fetch deduplication. Yes, set cache: no-store. But that only works for fetch requests. If you have a 3rd party lib doing the fetching (say, Google Firestore), then you have to declare export const dynamic = 'force-dynamic' at the top of your route segment: https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config https://nextjs.org/docs/app/api-reference/file-conventions/r... That behaviour wasn't documented when I got started with NextJS 13...imagine the fun I had trying to work out why I can't get updated data from the server. It was nuts.

dbbk 3y ago
Honestly this whole RSC/app router endeavour just seems like a mistake. So many strange buggy and undebuggable behaviours. To what end? We have a basic SSR React app and it serves millions of users while cached by Cloudflare. Works perfectly. KISS.
- ervine 3y ago
  Yep and it split the ecosystem / documentation / dev efforts / codebase. Should've been a different product.
- 0xblinq 3y ago
  It’s a pretty big fuck up actually
wyattjoh 3y ago
You can actually call `unstable_noStore()` from `next/cache` to do that without needing to set it on the segment level[1]! We're working on improving the DX around Dynamic API's to make it a seamless experience. [1]: https://nextjs.org/docs/app/api-reference/functions/unstable_noStore https://nextjs.org/docs/app/api-reference/functions/unstable...
- deleted 3y ago
  [deleted]