Thought/ideas: Do we have a community package of components/elements ?

I don't think this is practical, or even necessarily more efficient. Versioning will be a pain, what if packages need conflicting versions/features? There's no nice way for Vite and/or NPM to handle the dependency, so you'd have to rely on nuget to actually ship the component library dependency to the backoffice - which feels kind of wrong. Modern JS libs like ChartJS are supposed to be used with an "import only what you need" approach. If you want to provide a single shared version you have to import everything people might need. If multiple packages use only a subset you may find that importing the same small thing multiple times is better than importing the whole kit and kaboodle once.

Yeh fair point. I just have worries that we gonna have duplicated stuff in our installs

@Warren Buckley had the same idea as well, I will be using ChartJS for at least one package, maybe more in the future - I know workflow is using it. Not an expert here but if @Jason says its better that everyone shipts the own then it make sense 😄 At the end of the day the addition to the bundle is like 150kb which is far less than any avarage image today

We will, but I think that's actually the least worse option.