-
-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elysia fails to generate types when used with path aliases #887
Comments
I created this issue and this PR to warn users about this issue until I or someone figure out how to solve it. |
They shouldn't break nothing. |
I will provide a easy way to reproduce the issue. Do you know, in the meantime, where can I find the generated types from elysia/eden? |
It is not generated |
You can use the references property in tsconfig.json to include the tsconfig from the backend in the frontend. This is not an Elysia issue, this is a TypeScript configuration issue. |
What version of Elysia is running?
elysia": "^1.1.22
What platform is your computer?
No response
What steps can reproduce the bug?
bun create elysia app
tsconfig.json
. Ex:ElysiaJs
instance. The most obvious issue happens when you import anElysiaJs
instance that is used for route splitting.What is the expected behavior?
ElysiaJs
should know how to handle with import aliases. Independent of them being on a monorepo or not.What do you see instead?
Elysia type system breaks
Additional information
This might be happening on monorepos only. I will investigate once I find time and report back.
Have you try removing the
node_modules
andbun.lockb
and try again yet?Yes
The text was updated successfully, but these errors were encountered: