- Issue created by @prem suthar
- 🇧🇪Belgium StryKaizer Belgium
It looks like the best solution would be to have #2205027: VERSION in library declarations does not work for contributed/custom modules → commited in core, so we can cache our assets as best as possible.
- 🇮🇳India prem suthar Ahemdabad- Gujrat , Jodhpur - Rajsthan
You're absolutely right. Having #2205027: VERSION in library declarations resolved and committed in core would significantly enhance our ability to cache assets effectively. It would also bring more consistency and reliability when handling contributed and custom modules. This improvement could save both development time and resources while improving site performance. Let’s hope it gets prioritized soon!
- Assigned to nidhish
- Status changed to Needs review
about 17 hours ago 8:05am 12 May 2025 - 🇭🇺Hungary mxr576 Hungary
It looks like the best solution would be to have #2205027: VERSION in library declarations does not work for contributed/custom modules commited in core, so we can cache our assets as best as possible.
It could be, but until that is resolved, the current solution with
version: VERSIONleads to cache invalidation issues at client side and CDN level when only this module is updated.So heavy +1 on removing this constant usage for now and let Drupal to calculate the version of the asset based on the hash of the file for now.
See also the warning on https://www.drupal.org/docs/develop/theming-drupal/adding-assets-css-js-... →