Huge Bundle Size when import every module about ng-bootstrap HOT 7 OPEN

Hi @alexnoise79

OK, but the point of optimization: true is precisely to avoid having such huge bundles, and to remove what isn't actually used by the application.
Isn't it a bit weird to opt out of the mechanism designed to reduce bundle sizes and then be surprised about getting a big bundle size?

from ng-bootstrap.

Hi @jnizet

yes i l know, but is the only way to see all the module names

in any case even with optimization:false the bundle still contains all the modules, and this is wrong.

i updated the description, thanks

from ng-bootstrap.

It's not wrong. The optimization is precisely designed to tree-shake the bundles and remove the unused parts.
I don't understand what you mean by "is the only way to see all the module names".

from ng-bootstrap.

@jnizet

var NGB_MODULES = [NgbAccordionModule, NgbAlertModule, NgbCarouselModule, NgbCollapseModule, NgbDatepickerModule, NgbDropdownModule, NgbModalModule, NgbNavModule, NgbOffcanvasModule, NgbPaginationModule, NgbPopoverModule, NgbProgressbarModule, NgbRatingModule, NgbScrollSpyModule, NgbTimepickerModule, NgbToastModule, NgbTooltipModule, NgbTypeaheadModule];

from ng-bootstrap.

That is part of the unoptimized bundle. If you turn optimization on, it will be removed. That's what optimization is for.

from ng-bootstrap.

@jnizet

you are right, i checked the minified does not contain all, even if in some scenario i have "ngbDropdown" that have not been imported in other modules.

there is no way to tree-shake the unoptimized bundle?

from ng-bootstrap.

This is because the library has only a single entrypoint. For libraries ng-packagr will always produce chunks per entrypoint, and so loading a single module from this entrypoint drags the entire entrypoint into the bundle.

Some time ago I asked about this on StackOverflow, but still investigated everything myself. The library should be structured like this with entrypoints next to the src folder

from ng-bootstrap.