-
Notifications
You must be signed in to change notification settings - Fork 28
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
Support for importing multiple modules from a library with ONE statement #318
Comments
To be honest, I don't see how the current module layout would prevent tree shaking in general. If you refer to If we would have the module layout that you propose above
tools could indeed shake the tree and a lot of So I guess, your point is not really tree shaking, but writing less imports. That's a fair requirement and we indeed considered to add a layer on top of the current modules, most likely per package, not per library (means: one for I would hope/expect that such a layer just consists of re-exports, but we did not yet invest into it. As a precondition, IMHO the babel-plugin-transform-modules-ui5 would have to recognise and dissolve such re-export modules and rather generate the corresponding individual module dependencies in the |
Yes, you're right. I'm ok if this is currently not a prio for you and if it takes longer. I just wanted to report this to trigger a discussion/conversation about it. Thanks for the fast response :) |
Hi,
I just noticed that (control) imports cannot use tree shaking atm.
This means you need to write a very long "import header" like:
and cannot simplify write some short and concise code like:
Are there any plans to support this in the future?
The text was updated successfully, but these errors were encountered: