Needs review
Project:
Google Tag
Version:
2.0.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Apr 2026 at 17:06 UTC
Updated:
24 Sep 2026 at 09:12 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
telegraph commentedInitially attached the minified scripts here, but was eventually able to create an MR
Comment #4
telegraph commentedAs an alternative solution to providing minified scripts, could the scripts please be processed by the Drupal core CSS and JS aggregation/minification functionality?
Comment #5
telegraph commentedComment #6
jnycz commentedI am seeing the same flags in Semrush, one for each page so thousands in my case. Needed feature.
Comment #7
platinum1 commentedThe larger the site, the larger the impact...
Comment #8
berdirThis would be extremely annoying to maintain combined with other changes to those files like this.
I don't understand why preprocess is off for these scripts, it's been like that since the massive initial commit of the 2.x branch and I never understood why. So yes, does anything break if you just remove the preprocess flag? I'd also want to verify how this works together with the
#3565258: Support library-specific aggregates would allow for them to still be put in a separate aggregate file.
Comment #10
telegraph commentedMade an MR attempt at turning on preprocess and adding 'library-specific aggregates' as indicated in the linked issue
Comment #11
telegraph commentedComment #12
steinmb commentedlibrary-specific aggregates is introduced in version: 11.5.0 so if implemented, this version have to define 11.5.0 as minimum version?
Comment #13
berdirEarlier versions will just not optimize it accordingly and will include it in the many regular variations of the JS aggregates, but it should still work. I haven't manually tested that though.