tRPC v11, Netlify vs. Next.js, and Firefox Gets PWAs (Kind Of)
Hosted by
Share this episode 
Full Description
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. It remains to be seen if Firefoxâs unique take on PWAs will spur greater usage of them overall, but at least itâs another step toward browser parity. Long time css-in-js library styled-components announces itâs entering maintenance mode for a variety of reasons including incompatibility with RSCs, a general move away from css-in-js styling, and the core maintainer no longer actively working with styled components in his own products. Another new JavaScript runtime has hit the scene: Bare claims it can run on any device with minimal requirements and excels at apps that are peer-to-peer, decentralized, or high volume. And Netlify doubles down on its new foray into agent experience (AX), by partnering up with AI IDE company Windsurf to offer one-click deployments from a userâs Windsurf IDE. There's a beta version available for devs to try, and we'll keep you posted when we try it out.