5 ms·

Nice! I built something similar yesterday. But decided to use elysia instead. They have a tRPC like client with full TS support called eden. - eden: https://el

by crsr 1y ago

Nice! I built something similar yesterday. But decided to use elysia instead. They have a tRPC like client with full TS support called eden. - eden: https://elysiajs.com/eden/overview.html https://elysiajs.com/eden/overview.html

ilrwbwrkhv 1y ago
Not very good. The type safety thing doesn't work well when you are using it across different folders.
- tough 1y ago
  what do you mean by across different folders here? I was thinking about using elysiajs so this seems important
  - tough 1y ago
    would this hack help? https://stackoverflow.com/questions/79494287/is-it-possible-to-keep-type-safety-in-elysiajs-when-using-seperate-route-files https://stackoverflow.com/questions/79494287/is-it-possible-...
  - ilrwbwrkhv 1y ago
    I would reconsider using Elysia. I was also very excited by it and I thought it would be great but it has got errors and issues with different library versions and things like that. Also the whole Eden thing doesn't work for me for whatever reason. I have a monorepo. Typescript keeps complaining. Also if everything is defined in a single file, then it works well. If it's in different files, it breaks the whole type side of things.
- root_axis 1y ago
  Huh? It works fine across different modules. It helps to read the documentation thoroughly. I don't mean that to sound snarky, but it's likely you missed something if you're not able to modularize your route types.
tough 1y ago
would love to see it if open source!
threatofrain 1y ago
Elysia is sooo underrated. IMO they could improve their marketing by emphasizing they're compatible with other environments and not just Bun.
sharps_xp 1y ago
The main draw for me with elysia was that it maintains bun's perf benefits unlike express. When I got into the weeds of the documentation, their abstractions could use a lot of polish. The lifecycle of a request is not that clear imo and all the hooks you put into it look like hacks rather than integrations.

by crsr 1y ago

ilrwbwrkhv 1y ago

Not very good. The type safety thing doesn't work well when you are using it across different folders.

tough 1y ago
what do you mean by across different folders here? I was thinking about using elysiajs so this seems important
- tough 1y ago
  would this hack help? https://stackoverflow.com/questions/79494287/is-it-possible-to-keep-type-safety-in-elysiajs-when-using-seperate-route-files https://stackoverflow.com/questions/79494287/is-it-possible-...
- ilrwbwrkhv 1y ago
  I would reconsider using Elysia. I was also very excited by it and I thought it would be great but it has got errors and issues with different library versions and things like that. Also the whole Eden thing doesn't work for me for whatever reason. I have a monorepo. Typescript keeps complaining. Also if everything is defined in a single file, then it works well. If it's in different files, it breaks the whole type side of things.
root_axis 1y ago
Huh? It works fine across different modules. It helps to read the documentation thoroughly. I don't mean that to sound snarky, but it's likely you missed something if you're not able to modularize your route types.

tough 1y ago

would love to see it if open source!

threatofrain 1y ago

Elysia is sooo underrated. IMO they could improve their marketing by emphasizing they're compatible with other environments and not just Bun.

sharps_xp 1y ago

The main draw for me with elysia was that it maintains bun's perf benefits unlike express. When I got into the weeds of the documentation, their abstractions could use a lot of polish. The lifecycle of a request is not that clear imo and all the hooks you put into it look like hacks rather than integrations.