tRPC v11, Netlify vs. Next.js, and Firefox Gets PWAs (Kind Of)

Front-End Fire

Content provided by TJ VanToll, Paige Niedringhaus, Jack Herrington, TJ VanToll, Paige Niedringhaus, and Jack Herrington. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by TJ VanToll, Paige Niedringhaus, Jack Herrington, TJ VanToll, Paige Niedringhaus, and Jack Herrington or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

23d ago 36:53

MP3•Episode home

The tRPC team declares v11 officially production-ready. tRPC allows devs to build typesafe APIs with types that can be shared on the client and server, and now it has support for TanStack Query v5, the ability to send and receive non-JSON data content types, improved support for RSCs, and the ability to stream responses.

After the Next.js security incident a few weeks back, Netlify writes an open letter around the challenges Next.js poses when not hosted on Vercel. It raises valid points like a lack of adapters, no production grade documentation for serverless deployments, no visible roadmap or release schedule, and a disregard for open web standards, among others.

Firefox is finally adding support for progressive web apps (PWAs), but its web app support will intentionally not look, feel, or behave the same way similar features do in other browsers.

News:

Paige - tRPC v11
Jack - Firefox will support PWAs (finally)
TJ - Next.js Netlify deployment drama

Bonus News:

What Makes Us Happy this Week:

Thanks as always to our sponsor, the Blue Collar Coder channel on YouTube. You can join us in our Discord channel, explore our website and reach us via email, or talk to us on X, Bluesky, or YouTube.

93 episodes

#Tech #TJ VanToll, Paige Niedringhaus, Jack Herrington #Jack Herrington #Paige Niedringhaus #TJ VanToll