- Merge request !14203Add support for 'unique_css_aggregate' and 'unique_js_aggregate' → (Open) created by catch
Similar to ✨ [PP-1] Allow setting aggregation groups for js files in library definitions Postponed , but that issue is js-specific and also blocked on two bugs that are js-specific.
There are some CSS libraries that consist of multiple files (so worth aggregating) and either loaded on every page (or only loaded on very specific pages like one admin page, less interesting but worth thinking about).
The global theme library is the most obvious one.
We can add a library key like 'dedicated aggregate', and when we build CSS groups etc. put that library into a single aggregate, with a differently constructed URL that only contains the library, no delta, not the other libraries on the page. Most of the logic is already in the MR on ✨ [PP-1] Allow setting aggregation groups for js files in library definitions Postponed and should mostly need adapting.
This will maximise browser and CDN cache hit rates, because regardless of whatever other libraries on the page, not only the aggregate file path itself, but also the query arguments will be identical.
Once we've done this issue, we'll be able to add 📌 Use early hints for CSS Active on top - because we can then construct the specific URL for an aggregate that we know will be loaded on a page - before the entire page is built and all #attached are processed.
Active
11.0 🔥
asset library system
It affects performance. It is often combined with the Needs profiling tag.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.