2023-07-17
3046
#typescript
Ibiyemi Adewakun
174635
109
Jul 17, 2023 â‹… 10 min read

Using Protobuf with TypeScript for data serialization

Ibiyemi Adewakun Ibiyemi is a full-stack developer from Lagos. When she's not writing code, she likes to read, listen to music, and put cute outfits together.

Recent posts:

A crash course in Next.js middleware

A crash course in Next.js middleware

Learn the ins and outs of Next.js middleware, which allows you to perform actions before a request is completed and modify the response accordingly.

Temitope Oyedele
May 23, 2025 â‹… 9 min read
How AI Is Changing Debugging With Google Gemini

How AI is changing debugging with Google Gemini

The Google Gemini AI model has integrated AI-powered features to improve the debugging experience in web development.

Emmanuel John
May 23, 2025 â‹… 5 min read
10 Node.js 24 features you're probably not using

10 Node.js 24 features you’re probably not using

The Node.js 24 release included significant updates. Explore 10 features you might not be using yet — but absolutely should be.

Emmanuel John
May 22, 2025 â‹… 8 min read
six CSS animation libraries to bring your project to life in 2025

6 CSS animation libraries to bring your project to life in 2025

Explore six of the best, easiest, most configurable, and convenient CSS animation libraries available in 2025.

Murat YĂĽksel
May 22, 2025 â‹… 8 min read
View all posts

2 Replies to "Using Protobuf with TypeScript for data serialization"

  1. Very nice article! One observation is that the deserialized output doesn’t exactly match the originally defined object. Specifically, the original enum string values are replaced with numeric values, e.g., { “platform”: “WHATSAPP” } became { “platform”: 0 }, and { “relationship”: “FRIEND” } became { “relationship”: 0 }. How do you reconcile this? Is there a way to preserve the original string values for enums?

Leave a Reply