Adding third party library systems (such as for web components and pattern libraries) and customizing the behavior of assets (js / css parsing & collections settings) is difficult, if not impossible, with the current core system.
If a module wanted to add library support for additional systems, it would need to recreate core's library handling, and use a workaround (such as drupalSettings: {}) for libraries consisting only of new systems (see https://drupal.org/project/patternkit or any other module that attempts to add support for HTML fragment libraries).
The Asset Libraries system is over-complicated:
and over-specific:
Each item here will be created as sub-issues under this META issue's Remaining Tasks section to keep this issue centered on discussion and the sub-issues centered on implementation.
(reviews needed, tests to be written or run, documentation to be written, etc.)
None.
Addition of Library Plugin support.
None.
(Major and critical issues should have a snippet that can be pulled into the release notes when a release is created that includes the fix)
Postponed: needs info
10.0 ✨
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
#3299996: Rationalize asset aggregation interfaces → is related but I'm not seeing how a plugin system helps here.
Since this issue was opened, single directory components were added to core - I'm not clear how this overlaps or not with patternkit.
Further to that, I'm not sure why the libraries system would be used for something like this vs. adding a new YAML file (as was done for sdc).