2023-03-03
2644
#typescript
Omar Elhawary
142868
Mar 3, 2023 ⋅ 9 min read

Building a full-stack TypeScript application with Turborepo

Omar Elhawary Frontend developer and Linux enthusiast interested in user/dev experience, software architecture, design systems, and functional programming

Recent posts:

DesignCoder and the future of AI-generated UI

From sketches to code in minutes, DesignCoder shows how AI-generated, hierarchy-aware UIs could change the way developers prototype and ship apps.

Rosario De Chiara
Oct 7, 2025 ⋅ 5 min read

Would You Use If() functions in CSS?

It’s 2025, and CSS finally thinks logically. The if() function brings real conditional styling — no hacks, no JS workarounds. Here’s how to use it right.

Ikeh Akinyemi
Oct 7, 2025 ⋅ 16 min read
Typescript or Zod for Validation?

TypeScript vs Zod: Clearing up validation confusion

Learn when to use TypeScript, Zod, or both for data validation. Avoid redundant checks and build safer, type-sound applications.

Alexander Godwin
Oct 6, 2025 ⋅ 3 min read
Wasm 3 Before GTA 6 LogRocket Article

We got Wasm 3.0 before GTA 6: Meet the web’s new engine

Discover how WebAssembly 3.0’s garbage collector, exception handling, and Memory64 transform Wasm into a true mainstream web platform.

Ikeh Akinyemi
Oct 3, 2025 ⋅ 2 min read
View all posts

One Reply to "Building a full-stack TypeScript application with Turborepo"

  1. Thank you for this cool article. I’m not that much familar with monorepos. I would highly use it, cause the type sharing between front and back would be a real benefit. The problem which I actually don’t know how to handle is the deployment. Doesn’t the frontend and backend need the types package which is not deployed on npm or another registry? I don’t want to publish a npm package for each of my projects just for sharing the types… so my questions is can this be handled with turborepo? Or is it automatically handled by it?

Leave a Reply