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.
replyElysia is sooo underrated. IMO they could improve their marketing by emphasizing they're compatible with other environments and not just Bun.
replywould love to see it if open source!
replyNot very good. The type safety thing doesn't work well when you are using it across different folders.
replyHuh? 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.
replywhat do you mean by across different folders here? I was thinking about using elysiajs so this seems important
replywould this hack help? https://stackoverflow.com/questions/79494287/is-it-possible-...
replyI 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.
reply