Next.js 16.4 came out on October 6, so it's three days old as I write this. Most posts about it will list what changed. I'll do that too, but I also want to cover the parts people skip: what the framework still can't do, what you have to fix on your own side before the new stuff helps, and whether a one-person team should still build on it when your tools are priced in dollars and your customers pay in naira.
Everything below comes from the release posts, the docs, and a few write-ups from other teams. The links sit next to each claim and again at the bottom. I haven't moved one of my own apps to 16.4 yet, so when something is the Next.js team's claim about its own work, I say so.
The author made this story available to subscribers only. If you're new, create an account to read this blog on us.
OR