Tessera
Folgen

Sebastian Silbermann

@sebbie.dev

nextjs @vercel.com, @react.dev at night, @testing-library.com core | testing + a11y first | he/him

56 Posts1064 Follower181 Folgt
Next.js@nextjs.org · 2d ago

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 ↓

Ivan Akulov@iamakulov.com · 3w ago

Possibly one of the most impressive Safari bugs I’ve run into lately: Going back (with a swipe) in *any* React app that uses Navigation API freezes the page for three seconds. What’s fun is the main thread is not frozen, only the rendered page is.

Aurora Scharff@aurorascharff.no · last mo.

Cache Components surface errors as you build when something dynamic would block your shell, nudging you toward a more performant app. The shell loads instantly while dynamic parts stream, and on this demo every route lands in the green. We're working hard to make them easier to adopt!

BildBild
Aurora Scharff@aurorascharff.no · last mo.

My React Summit talk is up: What RSCs Can Do in Next.js Today. To show it, I built a music player, open source and deployed on an early preview of Next.js 16.3. 🎵 next-beats.dev Watch the talk for the full walkthrough, and check the key patterns in code below ↓ gitnation.com/contents/wha...

rich harris@rich-harris.dev · 2mo ago

There are two ways to resolve the cognitive dissonance of being on Twitter while also caring about all the awful shit happening because of Twitter 1. Leave Twitter 2. Stop caring Profoundly disappointing how many people I like seem to have chosen the latter

Sebastian Silbermann @sebbie.dev · 3mo ago

I personally would recommend reviewing actions/checkout with a custom ref input instead. actions/checkout is the way to escape trust boundaries. In pull_request_target events that's fork -> upstream. But in workflow_dispatch events actions/checkout allows running in protected GH environments.

James@43081j.com · 3mo ago

most of these github actions driven breaches are because of pull_request_target. here's some tips of what to look for when reviewing your own workflows. worth noting - it is safe, and necessary, when used correctly 🧵

Next.js@nextjs.org · 4mo ago

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...

Next.js Across Platforms: Adapters, OpenNext, and Our Commitments

Next.js 16.2 introduces a stable Adapter API, a public adapter test suite, and a working group for more consistent deployment across platforms.

nextjs.org

Nicolò Ribaudo@nicr.dev · 6mo ago

The "export defer" TC39 proposal aims to introduce a similar optimization *at the language level*, so that you can rely on it in all the tools and environments that you might run your code with. Just because you need one thing from a module, you shouldn't pay the cost of all the others!

GitHub - tc39/proposal-deferred-reexports

Contribute to tc39/proposal-deferred-reexports development by creating an account on GitHub.

github.com

VoidZero@voidzero.dev · 6mo ago

Why did adding ONE component make your build drastically slower? The answer is often: Barrel files. Luckily, you can enable Lazy Barrel Optimization in @vite.dev 8 and @rolldown.rs do bring your build time back to normal. Want to know more? Check the video & docs rolldown.rs/in-depth/laz...

Barry Pollard@tunetheweb.com · 6mo ago

From Chrome 145 (on general release next week!), DevTools we will start to show so called "soft" navigations and "Soft LCP" in the Performance Panel traces. These are for SPAs which don't do a full page load, but instead "fake it" by updating the current page and pushing a new history entry. 1/5 🧵

Screenshot of a performance trace in Chrome DevTools with a few additional "Nav*" and "LCP*" markers. Hovering over the "LCP*" shows this is a "Soft LCP" and in the Summary panel when you click on it you see "Soft Largest Contentful Paint" and a "Learn more about Soft Largest Contentful Paint" link.
Wyatt Johnson@wyattjoh.ca · 6mo ago

Just ported my personal site over to @astro.build with a custom @bun.sh adapter I wrote 🚀 👋 I'm currently looking for my next role, so if you're hiring, reach out! - Astro + Bun for blazing fast SSR - Supports ISR and SWR - Hosted behind @cloudflare.social github.com/wyattjoh/ast...

GitHub - wyattjoh/astro-bun-adapter: Astro adapter for Bun with optimized static file serving and ISR (Incremental Static Regeneration)

Astro adapter for Bun with optimized static file serving and ISR (Incremental Static Regeneration) - wyattjoh/astro-bun-adapter

github.com

Ryan Cavanaugh@searyanc.dev · 7mo ago

Your TypeScript year in review You "silenced" 417 errors with `as any` that turned into runtime errors as soon as the code ran TypeScript printed 4,693 error messages. 26 of them made sense You spent 98 minutes waiting for tsc to run. During this time you spent 544 minutes reading social media

Daishi Kato@daishikato.com · 8mo ago

⛩️ Waku v0.27.3 has been released. - Dependency updates addressing the critical React Server Components security vulnerability - Various small improvements All users should update immediately: github.com/wakujs/waku/...

Update instructions for CVE-2025-55182 · wakujs waku · Discussion #1823

References https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components https://www.facebook.com/security/advisories/cve-2025-55182 GHSA-fv66-9v8q-g76r Affected vers...

github.com

Paul Frazee@pfrazee.com · 9mo ago

One of the huge perks of working at a software company is, when there's something about the product that bothers you personally, you can get your hands dirty and find out why it's basically impossible to get fixed