Josh

Josh

@storyhb.com

Working on React and Next.js at Vercel

636 followers105 following215 posts

Josh reposted

Coding agents hit Next.js errors, unclear docs, and non-obvious workarounds while they build. They often solve the task and move on without reporting what failed. For Next.js 16.4, we created a new agent feedback system. 𝚎𝚡𝚙𝚎𝚛𝚒𝚖𝚎𝚗𝚝𝚊𝚕: { 𝚊𝚐𝚎𝚗𝚝𝙵𝚎𝚎𝚍𝚋𝚊𝚌𝚔: 𝚝𝚛𝚞𝚎, } Learn more about the feature ↓

Josh reposted

built Stamp, a Gmail-style inbox, to explore the new 𝚗𝚊𝚟𝚒𝚐𝚊𝚝𝚒𝚘𝚗() API in Next.js 16.4. Sometimes you want to cache content for return visits without prefetching it before someone opens the page. Live demo, source code, and docs below ↓

Josh reposted

Next.js 16.3 is now available! • Up to 90% less memory in dev • Faster builds, type checking, and rendering • Better tooling for AI agents • Custom error boundaries • Instant Navigations for SPA-like responsiveness nextjs.org/blog/next-16-3 Here's what's new ↓

Josh reposted

Building SPA-like experiences with Next.js (3) With Partial Prefetching, you can tap a link and the page arrives with its content already there. Live demo, source code, and docs below ↓

Josh reposted

Introducing eve, an agent framework. 𝚊𝚐𝚎𝚗𝚝/ 𝚊𝚐𝚎𝚗𝚝.𝚝𝚜 𝚒𝚗𝚜𝚝𝚛𝚞𝚌𝚝𝚒𝚘𝚗𝚜.𝚖𝚍 𝚝𝚘𝚘𝚕𝚜/ 𝚜𝚔𝚒𝚕𝚕𝚜/ 𝚜𝚊𝚗𝚍𝚋𝚘𝚡/ 𝚜𝚌𝚑𝚎𝚍𝚞𝚕𝚎𝚜/ Like Next.js, for agents. vercel.com/blog/introd...

vercel.comIntroducing eveIntroducing eve, the open-source agent framework from Vercel for building, running, and scaling agents in production, with durable execution, sandboxed compute, approvals, channels, tracing, and evals built in.

Josh reposted

Next.js 16.2: AI Improvements • Next.js-aware browser lets Agents improve your app • 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 included in 𝚌𝚛𝚎𝚊𝚝𝚎-𝚗𝚎𝚡𝚝-𝚊𝚙𝚙 by default • Browser errors forwarded to terminal • Dev server lock file prevents duplicate servers nextjs.org/blog/next-1...

nextjs.orgNext.js 16.2: AI ImprovementsNext.js 16.2 ships AGENTS.md in create-next-app, browser log forwarding, dev server lock file with PID, and next-browser for AI agent debugging.

Josh reposted

Next.js is used by millions of developers across every major cloud. Making it work well everywhere is on us. Here's what we've built with Netlify, Cloudflare, OpenNext, AWS, and Google Cloud, and the commitments we're making. nextjs.org/nextjs-acro...

nextjs.orgNext.js Across Platforms: Adapters, OpenNext, and Our CommitmentsNext.js 16.2 introduces a stable Adapter API, a public adapter test suite, and a working group for more consistent deployment across platforms.

Josh reposted

Josh reposted

Replying to @react.dev

Our thanks to the @react.dev team for informing us so that we could provide mitigation for our users. bsky.app/profile/deno...

Deno@deno.land

Next.js / React Server Components vulnerability identified. Apps deployed on Deno Deploy infrastructure are already protected by a runtime-level patch applied by our team. See this post for more information on how to protect your projects. deno.com/blog/react-s...

Josh reposted

Replying to @react.dev

Thank you to the React and Next.js teams for involving us early and for the clear communication. We were able to patch our network ahead of disclosure to help keep our customers secure. bsky.app/profile/netl...

Netlify@netlify.com

A critical vulnerability was recently disclosed in React Server Components (RSC), impacting multiple versions of React, Next.js and other RSC-based frameworks. This flaw could allow malicious actors to execute arbitrary code within an affected application. 🧵

Josh reposted

Next.js 16 • Cache Components • Turbopack enabled by default • Turbopack file system caching (beta) • Optimized navigations and prefetching • Improved caching APIs • Build Adapters API (alpha) • React 19.2 nextjs.org/blog/next-16

Josh reposted

i have some news. ✨ i’m occasionally available for React-adjacent consulting — architectural reviews, perf optimization, technical guidance. the format is hourly calls — a single call or possibly a series. email dan.abramov.consulting@gmail.com with what you need help on. i’ll reply if i can help.

I find it surprising that the answer to why 0! equals 1 is explained as “because it is convenient” when it would be trivially true if you defined N factorial to be 1 multiplied by N incrementing terms starting from 1

This is quite justifiable because 1 is the multiplicative identity. Starting from zero would be strange because then you’d have to add the multiplied terms to zero which seems more arbitrary since it requires a different operator. Anything else would just be even more egregious

So 0! === 1 is not just convenient its the simplest construction. It would be funny if 0! === 0 was convenient and then we had to justify the more complex construction but alas that is not the case

Holbox in LA. Michelin star. $5 Baja fish taco. Don’t make it make sense. Just eats tacos (and everything else)

Josh reposted

You are up to date.