elkjs and maplibre-gl included in bundle despite not using Graph/Map components

[jopelle1]

Hello,
We are using unovis (v1.6.4) in our Angular application.
Even though we are not using any components that require elkjs or maplibre-gl, these dependencies are still being included in our production bundle as lazy-loaded chunks.

Even though these librairies are not loaded at runtime, this is pretty annoying as it pollutes our bundle and makes our bundle size analysis harder.

I have a dirty workaround to fix this issue, which is adding these librairies to the externalDependencies angular option, but it is pretty ugly.

Are you considering fixing that behavior?

[rokotyan]

Unovis is tree-shakable. I don't know much about Angular's compiler config options, but most likely it can be enabled / configured there (in your project). Let is know if you think we're missing something, we always welcome contributions.

[jopelle1]

It seems that the issue comes from the fact that we are using esbuild, whose tree-shaking is not working properly with barrel files.
For example : evanw/esbuild#1698
I think the solution would be for Unovis not to use barrel files but it would probably be quite a bit of work.

[rokotyan]

@jopelle1 Thanks for investigation, this is valuable!

@lee00678 I wanted to suggest individual component imports but our Angular and other integration import from the main @unovis/ts entry point, e.g.:

unovis/packages/angular/src/components/line/line.component.ts

Lines 3 to 15 in 6f80298

	import {
	Line,
	LineConfigInterface,
	ContainerCore,
	VisEventType,
	VisEventCallback,
	NumericAccessor,
	ColorAccessor,
	ContinuousScale,
	CurveType,
	GenericAccessor,
	StringAccessor,
	} from '@unovis/ts'

If we update these imports to use individual files, then it should work.