I'm submitting a feature request
It would be nice, if output.libraryTarget could support the ES2015 module format.
What is the motivation / use case for changing the behavior?
Say I develop a fancy component called fancy-component with webpack. I use a very custom config with specific loader settings e.g. for inlining images and stuff like that. My module exports FancyComponent and BigFancyComponent.
A friend develops a single page application and uses rollup to do that. He knows nothing about webpack, but wants to use my FancyComponent, but not BigFancyComponent. He installs fancy-component and imports FancyComponent. BigFancyComponent should not be included in the build (because of tree shaking).
As far as I know this is currently not possible. My friend would need fancy-component in a format using ES2015 modules. But currently these include webpack specific loader logic. I really need to publish fancy-component without webpack specific logic, but with ES2015 modules.
I'm submitting a feature request
It would be nice, if
output.libraryTargetcould support the ES2015 module format.What is the motivation / use case for changing the behavior?
Say I develop a fancy component called
fancy-componentwith webpack. I use a very custom config with specific loader settings e.g. for inlining images and stuff like that. My module exportsFancyComponentandBigFancyComponent.A friend develops a single page application and uses rollup to do that. He knows nothing about webpack, but wants to use my
FancyComponent, but notBigFancyComponent. He installsfancy-componentand importsFancyComponent.BigFancyComponentshould not be included in the build (because of tree shaking).As far as I know this is currently not possible. My friend would need
fancy-componentin a format using ES2015 modules. But currently these include webpack specific loader logic. I really need to publishfancy-componentwithout webpack specific logic, but with ES2015 modules.