Skip to content
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

Is regenerator-runtime still required now that async functions are standard? #69

Open
owenkellogg opened this issue Oct 13, 2022 · 1 comment

Comments

@owenkellogg
Copy link

No description provided.

@swansontec
Copy link
Contributor

The thing that requires regenerator-runtime is the Webpack / Babel code transformation step. Since old Android phones have weak support for modern features in their WebViews, we do rely on Babel to make this compatible with really outdated feature sets.

One day, we would love to create our own WebWorker-style runtime inside our app, so we can decouple ourselves from the WebViews present on devices. For now, though, this is where we are stuck.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants