Well, I have thought about it... now that it's an organization, we might want to actually have different repos for the different subprojects, after all, I doubt many people use both Semantic-ui, Material-ui and elemental-ui.
while one might not use several at the same time, it would be really beneficial if we could add for the common stuff wrappers, so it only takes one line to change from Semantic-ui to Material-ui (as long as one is not using features that are only available in Material-UI e.g.)
I have, for instance, a wrapper I just started working on of tinymce, I could put it on this project, for sure, but it may just as well be in its own project, and not affect (or be affected by the others)
With this approach, my last wish is to have a way to declare required npm dependencies in an automatic way collecting dependencies from many scalajs libraries: to simplify the management in scalajs-bundler
Sure, I was thinking of wrapper for many libraries, you need to write in documentation the right version of the js dependencies and you should manually updated it in your build.sbt or similia in your project
If you release an material-ui react wrapper, you manually need to add the npm correct version.
Another solution is to version your wrapper with the version of the library and use an approach similar to yours: both jar/sjsr and npm have the same library version
Yup. MUI used to be generated in the old version as well, but it was done "off line" by @oyvindberg . I integrated his code into the main project and created generators for SUI and EUI as well, that's what the new 'gen' module does.