Performance impact of enabling cssCodeSplit for component library

[DarthSaul]

Are there any negative performance impacts or anything else to be aware of when enabling build.cssCodeSplit: true on vite.config?

The Vite docs indicate that cssCodeSplit defaults to false when utilizing Vite's lib build option. In my organization, I maintain a component library as part of our broader design system. We have teams consuming our library that don't want to import all of the styles for the entire library, i.e. importing @my-package/css/dist/style.min.css on main.js, because they only use a handful of the available components.

We've tested enabling build.cssCodeSplit: true, and this config seems to work for us -- a team consuming our library can install our npm package, import a component for use on some SFC, and the component's styles are included without having to import a @my-package/css/dist/style.min.css stylesheet on main.js.

However, my suspicion is that cssCodeSplit defaults to false when building a library for a good reason. I'm wondering, what might that reason be?

We maintain a Vue.js library, and utilize Vite's Library Mode.

Thanks!

[ivanjonas]

I am also curious about this. There must be a reason, but I can't find any documentation for it.