Testimonials / Love
Do you love or hate tRPC? Feel free to ping @alexdotjs on Twitter
From Twitter
For more testimonials, see this Twitter collection: https://twitter.com/alexdotjs/timelines/1441435105910796291
https://t.co/V4LL0ygDDB Looks super nice. Great lightweight alternative to @GraphQL when you don’t need the full power of the language and just to build endpoints. Vertical integration of server- and client-side TS also really slick.
— Nick Schrock (@schrockn) November 13, 2021
I have a strong affinity for technologies that don’t rely heavily on code generation. In that regard, TRPC is the only library that I have used that allows you to build a Full Stack API without it (albeit only with JavaScript). https://t.co/GF7YwPszla
— Ryan Edge 💙 (@chimon1984) November 6, 2021
Removed the GraphQL API in a project and replaced it with https://t.co/bzg9Mcbb07. End-to-end type safety across the desktop, mobile, and web apps without all the bloat and complexity 🔥 A super nice alternative for adding some Blitz-like DX to your existing apps 😍
— Lori Karikari (@LoriKarikari) October 2, 2021
Still not over the #tRPC hype. Rebuilt the entire Round API using it.
If you are building a dynamic app with Next.js, you should probably be using https://t.co/rvOMgdxyrq. It feels like @prisma for your APIs.
🧵Thread pic.twitter.com/OA61BSGhs3
— Theo (@t3dotgg) September 16, 2021
I am massively impressed by @alexdotjs‘s trpc.io:
end-to-end type-safety is awesome, but so is the simplicity of the architecture: It fits so nicely in my brain! And It uses GET requests for the queries!
I’m using it in production on @_snaplet, an am very happy
— Peter Cilliers-Pistorius (@appfactory) August 2, 2021
trpc is most impressive library I’ve seen for Typescript+Next.js in a long time trpc.io
If your app uses API routes between the UI and external APIs this is a super simple, clean way to handle it. No build steps.
I really hope this gains traction.
— Anthony Short (@anthonyshort) June 10, 2021
Hah, we just did our first endpoint, returned some mock data from a resolver and got instant autocomplete in the client. Everyone’s heads went 🤯🥳
— Marcus Rådell 🦀 (@marcusradell) June 10, 2021
If you don’t want to deal with the complexity of GraphQL and just want better type-safety across client & server (both TS) - trpc.io is pretty cool.
— Lorefnon (@lorefnon) June 6, 2021
From GitHub
We built a nextjs website with trpc and it has worked wonderful 🙌 […]
— cNille Aug 11, 2021
Hi - have just started using trpc and it is 👌 […]
— mmkal July 22, 2021
Hey @KATT - love the approach you have taken with this. Proper type sharing in Next.js projects is something I have been trying to achieve for a while and your solution here ticks all the boxes. […]
— dangreaves June 2, 2021
First of all I want to say thank you very much for making this library! I was already looking for a library like this for quite some time. […]
— simonedelmann May 17, 2021
Hi there, thanks for this library! I’m checking it out and appreciate how it feels like a much more lightweight approach to my typical Prisma-Nexus-Apollo-GQL Codegen stack. […]
— lostfictions June 24, 2021
Thank you for the quick fix and the amazing project 💯
— mgranderath May 3, 2021