-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
emitDecoratorMetadata is not working properly! #4575
Comments
I guess it is related https://github.com/oven-sh/bun/tree/dylan/emit-decorator-metadata |
Any update about this branch? |
I have the same issue. I was able to use a plugin to transpile files with decorators using TypeScript, which worked, but then ran into this issue #4689. For reference I'm currently using TypeGraphQL which relies on decorator metadata. |
This is blocking TypeGraphQL and TypeORM for us. @daniel-nagy Do you have the plugin you are talking about? Or is this something you cooked up? |
@Zikoat I'm using a fork of https://github.com/thomaschaaf/esbuild-plugin-tsc to support esm, see thomaschaaf/esbuild-plugin-tsc#20. Also see #5111. You would need to modify the plugin to always return the file content. |
Branch seems to have been merged on main: 4a1573e |
Bun v1.0.3 released with Just tried it MikroORM and it seem to work (I can clearly see metadata in compiled code and corresponding types in database schema). |
Fixed in Bun v1.0.3 🎉🎉🎉 |
I am not sure I should be writing it here or on #5000 I have a monorepo setting with a command to run from the root of the repository (it does not have
|
What version of Bun is running?
0.8.1+16b4bf341acc0f4804f0b6bdf5298c180cd00366
What platform is your computer?
Darwin 22.6.0 arm64 arm
What steps can reproduce the bug?
tsconfig.json
Here
reflect
isundefined
. It meansdesign:type
not reflected but in tsconfigemitDecoratorMetadata
is true. (I guess)emitDecoratorMetadata
is not working.What is the expected behavior?
No response
What do you see instead?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: