Latest note
Why Is My Next.js App Router Data Still Stale? Find the Cache Layer
Identify whether stale data comes from a cached fetch, rendered output, or a CDN response before choosing how to refresh it.
The Next.js notebook
Next.js Notes is a blog focused on Next.js. Read notes about the framework and use them as a starting point for exploring Next.js development.
Latest note
Identify whether stale data comes from a cached fetch, rendered output, or a CDN response before choosing how to refresh it.
Find the image response your browser displays, check whether its source is current, then choose a freshness strategy for the cache that serves it.
Use TanStack Query to request posts from an existing API endpoint and render pending, error, empty, and populated states.
Add an MDX file to a Nextra starter’s pages directory, register its filename in the starter’s navigation metadata, and check both the URL and rendered navigation.
Test and improve application performance
Add a Vitest component test for a Pages Router page, then distinguish its heading assertion from a route-level check.
Choose an application architecture
Keep stable Pages Router routes, and move routes selectively when App Router layouts, Server Components, or data fetching solve a real problem.
Test and improve application performance
Compare matched apps and explicit rendering modes, then report response, paint, and interaction measurements under repeatable conditions.
Create a GET and POST endpoint at /api/todos, call it with fetch, and check its JSON responses and status codes.
Secure and maintain an application
Check the version your project resolves, compare it with the advisory for the specific issue, and verify the fix after deployment.
Choose an application architecture
Choose Next.js for integrated routing and rendering options, or build a Vite-based React stack when a client-heavy app and control over its tools matter more.