You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 1, 2025. It is now read-only.
When using both, it seemed that the async methods in _createClass output lose the origin names, compared to the other non-async functions:
I found this was troublesome in some cases. Take runtime stack parsing as an example, now function was replaced by another function which name is not the same as original, hence we cannot figure out what function is really running at runtime(Because the error stack now shows at SomeClass.callee$ instead of at SomeClass.yourActualMethod )
I'm not quite sure about this transforming procedure machanism is done by babel itself or regenerator transform. An 'option' to preserve the function name, or providing enough infomation at execution will be really really helpful, thanks!
When using both, it seemed that the

async methodsin _createClass output lose the origin names, compared to the other non-async functions:I found this was troublesome in some cases. Take
runtime stack parsingas an example, now function was replaced by another function which name is not the same as original, hence we cannot figure out what function is really running at runtime(Because the error stack now showsat SomeClass.callee$instead ofat SomeClass.yourActualMethod)I'm not quite sure about this transforming procedure machanism is done by babel itself or regenerator transform. An 'option' to preserve the function name, or providing enough infomation at execution will be really really helpful, thanks!