---
title: "Discussion on \"tRPC: Your API and Your Client, Sharing One Type\" | Hashnode"
description: "Discussion on \"tRPC: Your API and Your Client, Sharing One Type\". Every team that builds a TypeScript API hits the same frustration. The server changes a field name, or a procedure starts expecting a different argument, and the client keeps calling the old shape. No"
url: "https://hashnode.com/posts/trpc-your-api-and-your-client-sharing-one-type/6af69849fc6c6063e6b97893"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [tRPC: Your API and Your Client, Sharing One Type](https://practicaldevblog.hashnode.dev/trpc-your-api-and-your-client-sharing-one-type?utm_source=hashnode&utm_medium=feed)

Every team that builds a TypeScript API hits the same frustration. The server changes a field name, or a procedure starts expecting a different argument, and the client keeps calling the old shape. No

5d ago · 7 min read · practicaldevblog.hashnode.dev  
Read the article

-   [#typescript](https://hashnode.com/tag/typescript)
-   [#trpc](https://hashnode.com/tag/trpc)
-   [#api](https://hashnode.com/tag/api)

## Written by

[Waqas Shahid](https://hashnode.com/@practicaldevblog)

@practicaldevblog

  
[View profile](https://hashnode.com/@practicaldevblog)

Practical tutorials, tools, and tips for developers.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
