Just like it was done with the /vendor folder in Drupal core I think third party frontend libraries should be declared as proper dependencies of the Drupal project instead of having them committed.
The tools to make this possible is what I think it should be discussed in this issue but I think there is many advantages in not requiring additional tools and just use composer for this.
There is an idea that would enable this kind of thing:
✨
Add a vendor:// stream wrapper
Postponed: needs info
Another solution would be to explore how to do it with npm/yarn since we already have a package.json file in Drupal. But that would require additional tooling to package Drupal and additional steps to have Drupal running from the git repo so my proposed solution is to first give a try to do this with composer.
Postponed
11.0 🔥
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This isn't really an asset system issue but more about the build process, moving to the JavaScript component where js and FEFM maintainers might have more opinions.
Postponing on ✨ Implement core management of 3rd-party FE libraries Active