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
SWC has a tick too much in transpiled for await
resulting in different output after transpiling
#1918
Comments
I was aware of such bug as you mentioned in the babel issue, but I prefer waiting for the babel team because I want to align the helper scripts. |
@kdy1 could you please review this pull request then for them? babel/babel#13491 they're just waiting for a review so they can merge |
I'm not a babel expert, so I expect my review to be helpless. |
You know how async transpilation works and I therefore think you're one of the few people that even understand what the changes are. I think they're not merging because there's like one more person on the planet that knows what it's about and they're on vacation. |
But I don't want to do it. |
I see, that's fair |
Update: that PR has now been merged |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Describe the bug
This exact bug: babel/babel#13490 but for SWC.
See this, output after transpiling and before transpiling should be the same:
Input code
Config
Expected behavior
Expected behavior is for the code above to output
like it does untranspiled.
Version
Additional context
I use SWC with parcel
Simple reproduction repository with SWC (kudos to @mischnic):
swc-for-await-repro.zip
Reproduction with parcel using SWC:
swc-for-await.zip
The text was updated successfully, but these errors were encountered: