This is the main point why Elysia exists Not performance, not fancy stuffs This problem is very real and I learnt it a hard way Type signature from your actual code IS the documentation not the other way around We spent ~3 years to perfect this

A lot of people are ok with writing input validation but not output validation This means that output is not described and not possible to document what API would returns Elysia fix that by using infer TypeScript type to schema NO MANUAL ANNOATION Your code is your schema

Interestingly, this problem is universal and ranks at 7th among all pain points with a JavaScript backend

Will try Elysia in my next project, any tips to start with the right foot?

Use the interactive tutorial

that openapi type spec is MINT dev x being able to integrate with other parts of your codebase NOT written in ts was the main reason i switched

Been taking the interactive Elysia tutorial, I can tell a lot of work went into building Elysia. The only bummer for me was the drizzle ORM setup, seemed a little too much just to get things working, maybe cuz most frameworks I've used come with built-in ORMs

what's this theme for vscode, looking so cool

Not VSCode, Zed Catppuccin Latte Blur

what Alien software do you use😭😭😭 Can u please tell me also

Anything that can self document my APIs instantly to this level is a blessing for any developer. It is an absolutely necessary factor of API frameworks now I feel, because the world moves so fast. I can't be sitting here documenting each and every endpoint!

using actual types as docs saves so many bugs

i really appreciate if the Nextjs team use elysia as a base so we get a good file based routing with more performance and cleaner syntax.

Other than the on-hover tooltips, can’t you do something like this in ts with zod-to-openapi?

What make this difference is that you don’t annotate output with zod or any validation library It is inferred from your code using type signature

What's been the biggest challenge in getting devs to trust type signatures as documentation? I've seen teams that religiously maintain separate docs even when the types tell the whole story.

does Elysia have middleware type propagation ?

I like this API documentation, and I also like this framework. It would be even better if there were more examples on the official website, just like NestJS.

documentation that lies vs code that can't lie. choose your fighter

Share your zed theme! it looks so good!

Catppuccin Late Blur