Post

Full end-to-end type safety across tech stacks is a dream for many developers. @craigory.dev makes it look easy. In his latest article, he shows how to achieve full-stack type safety in an Nx monorepo hosting a .NET WebAPI with a JavaScript frontend. nx.dev/blog/dotnet...

nx.devFull-Stack Type Safety Across Languages with @nx/dotnet | Nx BlogGenerate an OpenAPI document from a .NET API at build time, generate a TypeScript client from it, and let the Nx task graph keep the two in sync.

1/9/26, 3:00 pm3 reposts4 likes

kyisaiah47

@kyisaiah47.thecompound.tech

12 Sept

Bridging a .NET API to a JavaScript client usually exposes schema drift quickly. How are you checking the shared contract in CI?

kyisaiah47

@kyisaiah47.thecompound.tech

1 Sept

The seam between a typed backend and a typed frontend is where I lose the most time, generated clients drift the moment someone edits a DTO by hand. Curious whether the generation step here runs in CI or only on demand.

Craigory Coppola

@craigory.dev

Building the frontend regenerates the types anytime the backend has been modified, thus enforcing it in CI.

CyleWaitForIt

@cylewaitfor.it

1 Sept

@typescript.fm This feels like something @kamranicus.com would like.

Kamran Ayub

@kamranicus.com

2 Sept

I do something like this already actually but using my C# types -> TS types via a tool called Typewriter hehe.