Hendrik Liebau

I’m excited to share this: You can now build streaming Generative UIs – powered by the fabulous Vercel AI SDK – outside of Next.js. Here’s a simple demo I’ve deployed to AWS Lambda & CloudFront.

@Chakresh2005 @rauchg @timneutkens Do you have `cacheComponents` enabled?

@rauchg @timneutkens Could this be streamed in real time? As parts of the page become available, can they render progressively instead of waiting for everything? Right now it feels like the UI waits too long before showing anything.

Most irritating part with NextJs @rauchg

@alonzuman @vercel @vercel_support That’s fine to do, just mention it in the issue. Make sure to post the link here, then I’ll take a look.

@unstubbable @vercel @vercel_support i didnt submit it to the nextjs repo cuz it was a vercel specific issue, but ill try to repro tomorrow

got a @vercel bug that only happens on main branch???

@alonzuman @vercel @vercel_support Are you able to submit an issue with a repro for what you’re observing here? That would be very helpful! github.com/vercel/next.js…

@vercel figured it out, if anyone from the @vercel_support is seeing this - it seems to be related to parallel routes inside of route groups and the build cache (redeployed without using build cache and it worked)

@lubieowoce @feedthejim One-shot iterators definitely don’t pass the vibe check.

@feedthejim but be careful with stuff that crosses vibe boundaries, that can be tricky

👉 Introducing 'use vibes' We don’t know where it runs. You don’t know where it runs. But it feels right. Available now on next@canary.

@enricoros @feedthejim @dw60010009 @nextjs Thanks, that's helpful! We're looking into it.

I won't be able to repro; the app is using /app for two POST api routes (one on runtime=edge, one on node), and /pages with the traditional _document, _app, index, and 8 pages for the pages router. It's the head of github/enricoros/big-agi. Maybe the mixed nature is getting in the way?

Next.js 15.2 • Redesigned Error UI & Improved Stack Traces • Streaming Metadata • Turbopack Performance Improvements • View Transitions (experimental) • Node.js Middleware (experimental) nextjs.org/blog/next-15-2

@jaredpalmer I like debuggers. Logging = how does this system behave over macro time Debugger = Zoom in on a few moments

𝑓𝑢𝑛𝑐𝑡𝑖𝑜𝑛 𝐶𝑜𝑚𝑝({ 𝑖𝑑 }) { 𝑎𝑠𝑦𝑛𝑐 𝑓𝑢𝑛𝑐𝑡𝑖𝑜𝑛 𝑔𝑒𝑡𝑈𝑠𝑒𝑟𝐼𝑡𝑒𝑚𝑠(𝑖𝑛𝑑𝑒𝑥, 𝑙𝑖𝑚𝑖𝑡) { "𝑢𝑠𝑒 𝑐𝑎𝑐ℎ𝑒" 𝑟𝑒𝑡𝑢𝑟𝑛 𝑎𝑤𝑎𝑖𝑡 𝑑𝑏𝐺𝑒𝑡𝑈𝑠𝑒𝑟𝐼𝑡𝑒𝑚𝑠(𝑖𝑑, 𝑖𝑛𝑑𝑒𝑥, 𝑙𝑖𝑚𝑖𝑡) } 𝑟𝑒𝑡𝑢𝑟𝑛 <𝑈𝑠𝑒𝑟 𝑔𝑒𝑡𝐼𝑡𝑒𝑚𝑠={𝑔𝑒𝑡𝑈𝑠𝑒𝑟𝐼𝑡𝑒𝑚𝑠}/> } Here `id` will automatically become part of the cache key, and changing `id` will invalidate the cache even with same parameters. This is also why it can not be cache(fn) and has to be a compiler feature and be statically analyzable.

POV: When the spec for your implementation is literally a tweet. github.com/vercel/next.js…

@gao_jude In the request handler on the server, e.g.: #L41" target="_blank" rel="nofollow noopener">github.com/unstubbable/mf…

@unstubbable Where is asyncLocalStorage.run called?

In my RSC playground I've replaced the recently deprecated server context with a universal hook that utilizes AsyncLocalStorage on the server and client context in the browser, controlled through conditional exports. Good or bad idea? github.com/unstubbable/mf…

@alvarlagerlof You could even make this a universal useDebugLog with this little trick:

AsyncLocalStorage turns out to be very useful. I'm just learning about it so something about this implementation might be flawed (is it?). But it is already so useful.

@sebmarkbage I am always impressed by your long-term vision! 😆

@KnisterPeter @billylevin @devongovett @sebmarkbage Sure, but this is not what this whole discussion around github.com/facebook/react… is all about.

@gunnigylfa @jayphelps Two things to do when a colleague leaves their computer unlocked: 1. Post in Slack: “There’s cake at my desk! Come and get it before it’s gone.” 2. Run `brew install gti`.

@jayphelps brew install gti

git productivity booster life hack

@billylevin @devongovett @sebmarkbage If you want to be pedantic about it (as I am), 'parallel' is technically not correct. They are called sequentially, but not awaited sequentially.

@billylevin @devongovett @sebmarkbage In RSCs, there is no waterfall. The React Flight Server calls siblings in parallel.

@pawelblaszczyk_ True. I’m in favor of inferred types in local closures, but not for the public API of a module. As always: it depends.

@unstubbable And also a good argument for inferred return types - type predicates haha

There are so many DX goodies in this RC. 🥰 Among the many improvements, there’s also a good argument in there for the explicit-return-types camp (at least for exported functions).

window.matchMedia('(prefers-color-scheme: light)').matches &&

Working late at night, excited for the future. ▲

@alvarlagerlof Did you slip in an out-of-order streaming joke at the end there with “wtf”? 🤓

Fun fact: I coded most of this UI on a 10h flight. The WiFI was horrible and I couldn't really use any larger website, but the LLM worked just fine. Streaming wtf!