Sharing types between Go backend and TypeScript frontend: best practices and tools?

• goapi-gen

  1 115 1.9 Go

  This package contains a set of utilities for generating Go boilerplate code for services based on OpenAPI 3.0 API definitions

  

I usually have and OpenAPI document, and I generate both the client and server if I can. For the server, I specifically love goapi-gen.

• typescriptify-golang-structs

  7 474 3.0 Go

  A Golang struct to TypeScript class/interface converter

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• gots

  1 18 10.0 Go

  Discontinued No matter how you pronounce it, this repository is all about converting Go types to TypeScript types.

You can try GOTS

• social

  13 62 0.0 JavaScript

  social network in GRPC, Go, mysql, and vuejs, (by imran31415)

• protobuf-project

  3 16 7.6 TypeScript

  Protobuf with Go import paths for Go and TypeScript: project boilerplate w/ Makefile. Supports grpc, vtprotobuf, drpc, ts-proto, twirp, starpc.

  

• oapi-codegen

  64 5,178 9.1 Go

  Generate Go client and server boilerplate from OpenAPI 3 specifications

  

We're using https://github.com/deepmap/oapi-codegen at work while having an OpenAPI spec. When the spec changes, backend/frontend/mobile regenerate their server/client

Suggest a related project