Dennis
274 posts

Dennis
@typeweaver
Full-stack engineer. Loves TypeScript, Kubernetes and serverless. Yes, all three. Building OSS at https://t.co/RSjDyuh9AA. Currently focused on Typeweaver.
Stuttgart, Germany Inscrit le Mayıs 2014
157 Abonnements58 Abonnés

@GithubProjects OpenAPI YAML out, Zod in
github.com/rexeus/typewea…
Indonesia

@BatsouElef Very cool, I like your workflow!
Is the web app that we see in your video a product that you build yourself?
English

@typeweaver Done, I'm your 9th star!
It would also make my day if you could engage with this post. I work hard on it, and I show parts of my real work.
x.com/i/status/20443…
Eleftheria Batsou@BatsouElef
Today, I want to show you 2 real tasks of my daily work. (Building my personal brand and working as a Developer Advocate consultant.) This is how I leverage AI agents to be -way more- productive… My daily work includes: 1️⃣ Creating content on X (for my personal brand and for clients) 2️⃣ Customer acquisition strategy (for clients with SaaS/Startups) AMA after reading this thread👇🧵
English

@moshhamedani Going for a walk, or generally changing your focus, really works wonders.
English

If you get stuck, just take a break and go for a 5-minute walk. It helps you think outside the box. Yesterday I was stuck at my desk for several hours fixing bugs and refactoring code that was due to over-engineered architecture. The moment I walked out of the office, I could see things from a new perspective and realized a simpler architecture would make the code simpler, easier to reason about, and resolve all those weird bugs.
English

Building Typeweaver. It’s an Open Source dev tool.
I’ve had enough of maintaining big OpenAPI projects in YAML and love Zod/Typescript.
With Typeweaver you define your API once, generate runtime and client artifacts, and keep contracts consistent across your stack. All type safe.
Would love to connect! Also a star on GitHub would mean a lot
github.com/rexeus/typewea…
English

Building Typeweaver.
I’ve had enough of maintaining big OpenAPI projects in YAML.
With Typeweaver you define your API once, generate runtime and client artifacts, and keep contracts consistent across your stack. All type safe.
A GitHub star would mean a lot
github.com/rexeus/typewea…
English

Building Typeweaver. It’s an Open Source dev tool, so 0 MRR.
I’ve had enough of maintaining big OpenAPI projects in YAML.
With Typeweaver you define your API once, generate runtime and client artifacts, and keep contracts consistent across your stack. All type safe.
A GitHub star would mean a lot
github.com/rexeus/typewea…
English

@gailcweiner Mostly yes. Only the days where the workflow does not work as usual, because the agents do not follow the rules frustrates a bit.
English

@typeweaver @BatsouElef I have starred your Repository as it is inspiring
Also I am building Nexaview: A Dashboard for Weather, News, Calander, ToDo and more
Check out the Repository and please star it as it would mean so much
github.com/Temavrix/NexaV…



English

@jakobjelling Typeweaver. It’s a dev tool:
You define your API once, generate the runtime and client artifacts you need, and keep contracts consistent across your stack.
I’ve specified one too many large APIs in OpenAPI YAML.
A star on GitHub would mean a lot
github.com/rexeus/typewea…
English

You can’t register for my project, but you can give it a star on GitHub.
Typeweaver is a dev tool: you define your API once, generate the runtime and client artifacts you need, and keep contracts consistent across your stack.
I’ve specified one too many large APIs in OpenAPI YAML.
github.com/rexeus/typewea…
English

@csaba_kissi Tired of specifying large APIs in OpenAPI YAML? That’s where Typeweaver comes in.
Define your API once, generate the runtime and client artifacts you need, and keep contracts consistent across your stack.
github.com/rexeus/typewea…
English

Typeweaver is deliberately one-way for now: TypeScript/Zod as the single source of truth → clients, validators, routers, types, and OpenAPI specs (coming soon) fall out of that.
Here is a very early version of the documentation, separate from the READMEs in the repo.
typeweaver.dev
English

@typeweaver @mscode07 anyone who's spent time hand-writing OpenAPI YAML will immediately get this. does it go both ways — can you also generate from an existing API that has no spec yet?
English

Yep, unions stay intact on both sides. Zod schemas go in, narrowed types come out for requests and responses alike.
Where it really pays off is the client: every operation has a dedicated RequestCommand, and send() returns a union that narrows on response.type. That locks request shape ↔ response shape together in the type system, validated at runtime. You literally can't mishandle a response the API couldn't return.
Heads up: docs are still early outside the repo READMEs, not officially public yet, but here's the relevant page: typeweaver.dev/docs/client-us…
English

@typeweaver @1Umairshaikh auto-generating type-safe clients from Zod is the piece monorepo teams keep reinventing manually. does it handle discriminated unions or is that where things get messy?
English

@brankopetric00 It's nice when everything scales directly, it's not that complicated to set up
English
















