<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>tRPC Blog</title>
    <link>https://v12.trpc.io/blog</link>
    <description>Releases, deep dives and lessons learned from building tRPC, by the people who maintain it.</description>
    <language>en</language>
    <lastBuildDate>Fri, 21 Mar 2025 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://v12.trpc.io/blog/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Announcing tRPC v11</title>
      <link>https://trpc.io/blog/announcing-trpc-v11</link>
      <guid isPermaLink="true">https://trpc.io/blog/announcing-trpc-v11</guid>
      <pubDate>Fri, 21 Mar 2025 00:00:00 GMT</pubDate>
      <description>Although tRPC v11 has been production-ready for a long time via the @next tag, we&apos;ve gotten kinda addicted to adding new features without being sticklers to semantic versioning. Today, we&apos;re excited to finally be ripping off the band-aid and announcing the official release of tRPC v11!</description>
      <dc:creator>tRPC</dc:creator>
    </item>
    <item>
      <title>Introducing the new TanStack React Query integration</title>
      <link>https://trpc.io/blog/introducing-tanstack-react-query-client</link>
      <guid isPermaLink="true">https://trpc.io/blog/introducing-tanstack-react-query-client</guid>
      <pubDate>Mon, 17 Feb 2025 00:00:00 GMT</pubDate>
      <description>We are excited to announce the new TanStack React Query integration for tRPC is now available on tRPC&apos;s next-release. Compared to our classic React Query Integration it&apos;s simpler and more TanStack Query-native, choosing to utilize the QueryOptions and MutationOptions interfaces native to TanStack React Query, instead of wrapping useQuery and useMutation with our own client.</description>
      <dc:creator>Julius Marminge</dc:creator>
      <dc:creator>Nick Lucas</dc:creator>
    </item>
    <item>
      <title>Using Server Actions with tRPC</title>
      <link>https://trpc.io/blog/trpc-actions</link>
      <guid isPermaLink="true">https://trpc.io/blog/trpc-actions</guid>
      <pubDate>Thu, 23 May 2024 00:00:00 GMT</pubDate>
      <description>The builder-pattern for creating procedures which was introduced in tRPC v10 has been massively appreciated by the community, and many libraries have adopted similar patterns. There&apos;s even been coined a term tRPC like XYZ as evidence of the growing popularity of this pattern. In fact, the other day I saw someone wondering if there was a way to write CLI applications with a similar API to tRPC. Sidenote, you can even use tRPC directly to do this. But that&apos;s not what we&apos;re here to talk about today, we&apos;re going to talk about how to use tRPC with server actions from Next.js.</description>
      <dc:creator>Julius Marminge</dc:creator>
    </item>
    <item>
      <title>Writing a tiny tRPC client</title>
      <link>https://trpc.io/blog/tinyrpc-client</link>
      <guid isPermaLink="true">https://trpc.io/blog/tinyrpc-client</guid>
      <pubDate>Tue, 17 Jan 2023 00:00:00 GMT</pubDate>
      <description>Ever wondered how tRPC works? Maybe you want to start contributing to the project but you&apos;re frightened by the internals? The aim of this post is to familiarize you with the internals of tRPC by writing a minimal client that covers the big parts of how tRPC works.</description>
      <dc:creator>Julius Marminge</dc:creator>
    </item>
    <item>
      <title>TypeScript performance lessons while refactoring for v10</title>
      <link>https://trpc.io/blog/typescript-performance-lessons</link>
      <guid isPermaLink="true">https://trpc.io/blog/typescript-performance-lessons</guid>
      <pubDate>Sat, 14 Jan 2023 00:00:00 GMT</pubDate>
      <description>As library authors, our goal is to provide the best possible developer experience (DX) for our peers. Reducing time-to-error and providing intuitive APIs removes mental overhead from the minds of developers so that they can focus on what&apos;s most important: great end user experience.</description>
      <dc:creator>Sachin Raja</dc:creator>
    </item>
    <item>
      <title>Announcing tRPC v10</title>
      <link>https://trpc.io/blog/announcing-trpc-10</link>
      <guid isPermaLink="true">https://trpc.io/blog/announcing-trpc-10</guid>
      <pubDate>Mon, 21 Nov 2022 00:00:00 GMT</pubDate>
      <description>tRPC provides a great developer experience by enforcing tight, full-stack type bindings through the power of TypeScript. No API contract drift, no code generation.</description>
      <dc:creator>Alex / KATT 🐱</dc:creator>
    </item>
    <item>
      <title>Introducing tRPC</title>
      <link>https://trpc.io/blog/introducing-trpc</link>
      <guid isPermaLink="true">https://trpc.io/blog/introducing-trpc</guid>
      <pubDate>Wed, 05 May 2021 00:00:00 GMT</pubDate>
      <description>tRPC gives you end-to-end type safety from your (node-)server to your client, without even declaring types. All you do on the backend is that you return data in a function and on the frontend you use said data based on the endpoint name.</description>
      <dc:creator>Alex / KATT 🐱</dc:creator>
    </item>
  </channel>
</rss>
