Problem/Motivation
As stated in #3050389: Remove dependency to Classy from core themes, Classy will be moved to contrib before Drupal 9 and we have to remove dependencies on Classy from all core themes.
Part of this process includes creating theme-specific copies of all Classy libraries to core themes. This ensures Classy can be removed without impacting those themes.
Proposed resolution
- As needed, copy libraries and assets from Classy to Claro.
- Create new libraries for every copied library, named with the convention "classy.
".
- Override the Classy libraries so they are not loaded by Claro.
- Any Classy libraries-extend: should now be taken care of in Claro.
The end result is no Classy library assets should load, and Claro experience should be unchanged.