Importmaps are javascript files that list exports to load bundled modules.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/im...
I am thinking that using import maps might be a better solution than using libraries. Vite would compile all your libraries into an importmap and we could use this instead of referring to package.json. Your main library would just include the import map.
There are some experimental modules for this:
*
https://www.drupal.org/project/importmap →
*
https://www.drupal.org/project/importmaps →
Here's the relevant core issue: https://www.drupal.org/project/drupal/issues/3398525 ✨ Add an API for importmaps Active
This is a way to get more compatibility with code that is using js modules across Drupal. Maybe we can get the ball rolling at the theme level with vite since it can already be configured to set it up.
Active
1.0
Code
If this does happen I would really like it to be a configurable option. If a module/theme/whatever has a dependency with many levels of sub-dependencies, the cascading imports will be an unacceptable performance burden in my opinion.