Inlay

Profile

💼 Engineer integrating web frameworks @netlify.com 🔨 Open source maintainer @npmx.dev 🏡 https://philippeserhal.com

Philippe Serhal

"Open source is not just about code, it's about the people that make the code work", @zeu.dev sharing the ATProto parts of npmx at #Atmosphereconf

After years of working in silos, in 2024 @netlify.com, @cloudflare.social, OpenNext, Google @firebase.com, and the @nextjs.org team at @vercel.com built bridges. We started discussing how to truly solve for full portability of Next.js. And we kept at it. Today marks a culmination of this work.

1/ post from the @nextjs.org team at @vercel.com > Next.js is used by millions of developers, and many of them run on infrastructure that isn't Vercel. They deserve the same level of reliability and the same access to new features. Thank you to @feedthej.im for relentlessly leading this push ❤️

Just found this gem of a proposed conf talk title in an old brainstorming doc: Don't Ship Where You Vite? Actually, Do: A Case for Vite Deployment Plugins I can't believe I didn't go with that.

Fun fact: the Next.js brand guidelines [1] state "Using Next as a pun for Next.js should be done sparingly and in good taste." I am of course under no obligation to abide by these guidelines myself, but.. I gotta yell you, this has been a tough one to follow. [1] vercel.com/geist/brands...

Props to @t3.gg for contributing $5K to @e18e.dev! Looking forward to seeing all the creative ways @npmx.dev can collaborate with @e18e.dev to make the web faster, leaner, and simpler. We already have a bunch of things in the works 👀.

2/ post from the OpenNext initiative > Over the last three years, OpenNext has played a crucial role in pushing Next.js toward true portability. Now, the introduction of the Adapters API signals a new era. Thank you to @conico974.bsky.social @cloudflare.social and the whole OpenNext team.

3/ post from Google Cloud > When a security vulnerability is patched in the framework, we no longer have to worry that the fix will break a reverse-engineered API So happy to have been collaborating with you @jamesdaniels.net! > This is a major milestone, but it’s just the beginning.

4/ post from @netlify.com > We’ll continue working with the Next.js team, with our fellow OpenNext members (SST, Cloudflare, and independent OSS contributors), Google, the new Ecosystem Working Group, and with the broader ecosystem to tackle these remaining challenges. Thank you, everyone.

Brittany Ellich

Philippe Serhal

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

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

💭 This "webring" of multiple interlinked simultaneous blog posts across companies and groups was inspired by the recent @npmx.dev alpha launch! (npmx.dev/blog/alpha-r...)

Philippe Serhal

The Next.js Adapter API is now stable. That’s a big step toward running @nextjs.org across platforms. However, there's still work ahead and that's why we're forming the Ecosystem Working Group. @philippeserhal.com shares what’s next: www.netlify.com/blog/the-nex...