Some static error classes might be omitted when using decorator metadata #8684
Replies: 4 comments 1 reply
-
|
It might be related to oxc-project/oxc#20368, oxc-project/oxc#20369 |
Beta Was this translation helpful? Give feedback.
-
|
Does setting You have |
Beta Was this translation helpful? Give feedback.
-
|
The title of this discussion mentions |
Beta Was this translation helpful? Give feedback.
-
|
I created a PR regarding this issue. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! I'm one of the maintainer of Misskey, a federated microblogging platform built with TypeScript.
I'm currently trying to bundle and minify backend using Rolldown to improve memory consumption, as the whole code will be stored on memory when running the server.
misskey-dev/misskey#17068
However, the server was not launched (not all modules are loaded and stuck forever) until @babu-ch provided a fix:
kakkokari-gtyih/misskey#2
This pull request moves some of the custom
Errorclass defined as a static member of the class, to a root level. After this patch, the backend successfully up and started running.While I can now proceed to migrate build steps to rolldown, I'm curious if this is a bug related to rolldown or upstream tools (i.e. oxc). The following points are worth noting:
One tricky point is that this project uses NestJS, and therefore decorator metadata is in use.
Any suggestions or insights are much appreciated, thank you for the awesome tooling for JavaScript!
Beta Was this translation helpful? Give feedback.
All reactions