We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What if nanobundle is gonna be bundler-agnostic and can take advantage of SWC instead of esbuild as configuration?
The text was updated successfully, but these errors were encountered:
Heard that SWC is needed for more compatible output for legacy browsers.
Sorry, something went wrong.
The unbundle mode (#166) implies using an additional bundler, so it's not a legitimate motivation.
On the other hand, swc doesn't yet provide a stable bundler API. Parcel also does not expose a suitable API for custom incremental builds (#49).
I'm closing the issue because this has fairly low possibilities and I couldn't find a clearer motivation.
No branches or pull requests
What if nanobundle is gonna be bundler-agnostic and can take advantage of SWC instead of esbuild as configuration?
The text was updated successfully, but these errors were encountered: