-
-
Notifications
You must be signed in to change notification settings - Fork 418
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
[building-webpack] Consider removing async function transformation #140
Comments
I tested this by removing:
and adding:
to my demo app. I tested on the following browsers (on browserstack):
where everything works. Bundlesize savings: with fast-async without fast-async |
Thats great, thanks for testing! Performance is probably better too. |
Very slightly, yeah |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Open Web Components! |
In our webpack setup we use the
fast-async
plugin to compile async functions. However that makes it always kick in. Based on: https://caniuse.com/#search=async%20function any browser which supportstype="module"
supports async functions.Probably we can remove this transform, but we should properly test this.
The text was updated successfully, but these errors were encountered: