Next.js 16.3.1

Next.js 16.3.1 just dropped — one week after 16.3.0, because that's how the 16.x line rolls. I've been poking at it since the backport PRs started landing, and honestly? It's mostly a "stop the bleeding" patch. Which, let's be real, is exactly what a framework needs the week after a big release.

TL;DR

• Turbopack HMR fixes for dynamic imports evaluated from layouts — that weird "my page didn't update" thing? Probably fixed.
• next/image preserves the image response after optimization now. No more double-fetch weirdness.
• styled-jsx styles actually show up in Pages Router SSR on adapter builds again.
• The live headers() view of the incoming request is restored.
• Cache invalidation got brain surgery — only cache entries that predate a tag revalidation get discarded, and completed entries get reused instead of re-fetched.

The Good Stuff

'use cache' files can now export literals. Sounds minor, sounds boring — but it unblocks a whole class of config-style modules that previously made the compiler scream. Also, the dev validation worker stays alive across HMR updates now, which means fewer "wait, why didn't it re-validate?" moments in local dev.

And they fixed the Nav Inspector request loop on repeat captures, plus the optimistic-routing bugs that caused repeated prefetch loops. If you've ever watched your network tab fill up with duplicate prefetches, you know exactly which fix I'm talking about. That one's personal.

The "Eh" Stuff

There's the usual backport pile: an @swc/helpers bump, middleware redirect routes compiling up front in dev, unstable_cache item names getting properly encoded. Necessary, unexciting, moving on.

Should You Update?

Yes. It's a patch release — low risk, real fixes. npm i [email protected] and get on with your life. If you hit the prefetch loop bug or the styled-jsx thing, this is your fix. If you didn't, you're still on the supported track, which is the whole point.