Next.js 15 introduces significant changes to caching, particularly around the fetch function, API routes, and client router cache. While the intention is to improve the developer experience, some changes may be confusing and unintuitive, especially for newer developers. The update aims to make caching more transparent, with fetch requests, G Route handlers, and client router cache no longer caching by default. However, developers may need to force certain pages to be dynamic to achieve desired behavior.

13m watch time
6 Comments

Sort: