make lib tree-shakable

[nonlinearcom]

Hi, after adding vue3-openlayers as a plugin to a clean Nuxt project, the client bundle shows a large file (vue3-openlayers.es.js) of over 1MB. The same issue occurs when performing selected imports, like import { Map, Layers, Sources } from "vue3-openlayers (975 KB).

Is it possible to reduce the size of the bundled package? 🤔

├── ol-contextmenu@5.5.0
├── ol-ext@4.0.23
├── ol@10.1.0
├── vue@3.4.38 invalid: "latest" from the root project
└── vue3-openlayers@11.1.0

To Reproduce
Steps to reproduce the behavior:

Reproduction repo

Run npx nuxi analyze

Screenshots

[YXYH-12138]

Yes, I have encountered the same issue, and this library cannot be tree-shaken.🤔

[d-koppenhagen]

Hey, would like to contribute and refactor it? I think it would be acceptable if a Breaking Change is introduced. The best in my opinion would be to allow to import / load components individually and therefore expose them.

[vincerubinetti]

Hmm this is a bit concerning.

I have a SPA Vue app using Vite. Using vite-bundle-visualizer, I get this:

It looks like this package is taking up ~1.5 MB (uncompressed) and OL itself ~2 MB. In the OL breakdown, I think those sub-assets are only ones I'm actually using (though I'm not using the webgl renderer as far as I know). Not sure how much of that 1.5 MB is necessary vs un-necessary.

Over-the-wire, both libraries together are about 750kb, which is pretty bad.

Also notice that I still have leaflet installed (I'm currently transitioning to OL), and it's way way smaller. But Open Layers does have way more functionality than Leaflet.

---

Does anyone have a direct bundle size comparison between using this package and using OL directly?

Edit: I switched off from this library to just raw OL, with the exact same features (plus a couple extra), and can make a direct comparison:

OL now only takes up ~1.5 MB (uncompressed). Still a lot, but 0.5 MB less than when using this package... probably due to only importing the things from OL I needed. And then I of course don't have the MB of this package.

Overall, the transition was a good experience and only cost me ~70 extra lines of code to achieve the same thing.