Document that aggregation of JavaScript files can cause redeclaration

Add a step, which may not be obvious to non-Leaflet users: "Add a Geofield to a content type, and use Leaflet to show the map".

Make it simpler to replicate, by not requiring a custom module.

fwiw aggregator.module is the feed reader that's no longer in Drupal core.

Excluding those files from aggregation seems like the right fix to me. I'm not sure there's a way for the aggregation system to fix this if they're both declaring global constants.

That was also my hunch, since starting to rename constants or variables can easily end up being messy. I added a note in Checklist for launching a site → . Ideally, a dedicated Performance page under https://www.drupal.org/docs/administering-a-drupal-site/managing-site-pe... → would be best.

PS. Thanks for correcting the category. Wouldn't it be great if each Component had a short description, or page which listed the content under that Component? I'll create an issue.

I created ✨ Document each Component, make them searchable Active .

I created a new Aggregate CSS and JS files in Drupal core → page under "Performance", adding a workaround to the JS aggregation problem.

I hope someone can add a menu point to it, and maybe place it at the top, before the "Blazy" contrib module solution? (Changing status, to hopefully get this done)