Problem/Motivation

The asset aggregation system has several services/interfaces involved to make different parts swappable.

Unfortunately, as #1014086: Stampedes and cold cache performance issues with css/js aggregation shows, you can't actually swap one service out at the moment depending on what you're changing you usually have to swap 3-4 different things out. The interfaces were just added to match the original implementation, not really to support multiple different implementations.

Steps to reproduce

Proposed resolution

Consider merging the asset resolver + js + css group optimizer classes into a single interface, since these are so interdependent. There might end up being other changes involved as well

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

catch created an issue. See original summary.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.