-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Feature Request]: extend onResolve
plugin hook to include import attributes in import-statement
#3639
Comments
This was referenced Jun 19, 2024
This was referenced Jun 30, 2024
This was referenced Jul 10, 2024
This was referenced Sep 7, 2024
This was referenced Sep 17, 2024
This was referenced Sep 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
esbuild is not strong in splitting chunks. some related issues (#16, #207, #1781, #2208, #2227, #2419)
if the
onResolve
hook would have the entire import information a plugin could implement much better splitting strategy based on native imports.The idea is, if a plugin can collect all the imported named symbols from a specific
import-statement
request, it could externalize the request and generate aesm
bundle (with correct exports) from acjs/umd
module like react.my goal is to optimize large code base watch mode by externalizing modules to separate builds.
The text was updated successfully, but these errors were encountered: