Looking forward to the strict by default!

Any chance we can see MCP server support in iOS? Would beat Claude to the implementation if you could 👀

Absolutely. I’m using with Deno and it’s just the most pleasant thing. The automatic docs are a game changer.

It feels like the Go module authoring flow, but streamlined for Typescript. Even their publishing from GitHub Action's is like a one-liner 🤯

Yeah I found that rule recently, it finds a lot of cases, but I was hoping for deeper knowledge of the AST graph that also looked at subsequent calls `await` and understood, but eslint is more of a "single-file-pony" kind of linter 😅

What did you use to generate this 😍

That's where the magic of `use cache` comes in, the component itself can just have that directive added and the results of that component/function will be cached according the the lifetimes specified within it. We're looking for feedback though, open a discussion with questions :)

The new primatives like `use cache` are designed to simplify the caching experiences for Next.js. Lots of neat things coming that are currently still behind experimental flags.

What part of PPR do you find strange? Would love to help explain ☺️

Did you switch it to Go 😅

How do you use after for A/B testing 👀

We're either looking at making it work via a client side fetch perhaps (similar to how @astro.build does with their server islands approach) which wouldn't require any special features.

Other CDN's could support PPR natively, which is sort of a form of Edge Side Includes, but that's about it.

3.) The responses are always streamed, so in the case of being served from Vercel, we can do streaming compression for the content on the same stream.

2.) The static shell is just HTML that's outputted by Next.js, the same as what SSG would be, but just the static parts of the page, hence the "static" name of the shell. It would include the fallbacks if the children accessed request data.

Think of "use cache" like another way of writing unstable_cache, but with way more features. Anything that's wrapped in "use cache" can access things like I/O (fetch or fs) and not be considered dynamic.

Of course! Glad it was helpful :D