Alternative solution for advanced aggregation css / js

Hi
Any words on this?
IT is not working properly on my end either

Hi,

Could someone please provide an update on when we can expect a new release addressing the issue in above Drupal 10.1 version?

In the meantime, are there any alternative modules available that can serve a similar purpose and are compatible with Drupal 10.1? Any suggestions would be greatly appreciated.

Thanks

Looks like this module is unusable for anything beyond 10.1. This is a major issue to say the least. Can the maintainer or anyone provide updates? Or is there another recommended module? Can we expect a working version at some point? Thanks!

Drupal core covers nearly everything that advagg has done as of 10.1 - both async aggregate generation and minification of JavaScript, so you should be fine to just disable advagg and use core's css and js aggregation. There are further improvements to core's aggregation as of 10.3.x too.

Three effective solutions to optimize CSS and JavaScript in Drupal 10:

1. Lazy Loader
Defers loading of off-screen images and iframes until they enter the viewport, improving initial load times and conserving bandwidth, especially for mobile users.

2. CDN Module
Delivers static assets (CSS, JS, images) from servers closest to the user, reducing latency and enhancing performance for a global audience. Ideal for high-traffic sites.

3. Minify JS and CSS
Removes unnecessary characters and whitespace from JavaScript and CSS files, resulting in smaller file sizes and faster load times. This is crucial for sites with extensive scripts and styles.

I think this is sort of duplicate of https://www.drupal.org/project/issues/advagg?categories=All →

But yes, seems this project stalled with Drupal 10.1+

Is this module still alive? it looks dead.
any updates from authors?

Thank you

See discussion on 📌 Support new core JS/CSS aggregation process in core 10.1.x+ Needs review - most (nearly all) of the features this module provides are now covered in a different way in Drupal core, since Drupal 10.1.

Automatically closed - issue fixed for 2 weeks with no activity.