Post

Next.js 16.3 Preview: Instant Navigations A new suite of tools that brings the responsiveness of client-driven SPAs to Next.js, without giving up what Server Components do best. The speed of the server, with the feel of the client. Try it and tell us what you think ↓ nextjs.org/blog/next-1...

This entire premise is flawed.

in what way?

I'm even lost about what happens to the recent now "old" loading page 🤡

nothing, that’s used as a shell when available

But what's the actual priority to fix existing issues related to it? And why the only skill available mentions to not use it when using... cache? It's seems conflicting, the new instant is cached enforced. github.com/vercel/next.... github.com/search?q=rep...

@ricky.fm put a lot of effort into solving and communicating this problem with the async client stuff (hint: pending states!), so I know I'm not alone in feeling this way.

i see! i’d say the post intro describes two ends of the spectrum, but the actual model described in the post is more flexible. it’s more like ability to enforce which navigations have no async gap. having a guarantee like this is important, especially if routes need to work offline or w/ bad latency

I agree, the instant navigation is an interesting mechanism – this is effectively closing the "SPA" gap that the app router hasn't historically supported (where the whole router is navigable without internet). But it's still focused on shells and loading states, when I think that's missing the mark