Remove VERSION from libraries.yml

Open on Drupal.org →

Created on 22 January 2025, 8 days ago

Problem/Motivation

The version: VERSION lines in libraries.yml are creating a version query string using the Drupal Core version number for the asset files, making these files cached in the browser dependent on the Core version.

Steps to reproduce

This can produce various problems after an update, as the old versions of assets might be loaded for users who have those cached. The only way to currently fix those to clear the browser cache.

Proposed resolution

Remove the version: VERSION lines from libraries.yml. By doing this, Drupal will use an automatically generated query string added to filenames. From the code documentation:

The string changes on every update or full cache flush, forcing browsers to load a new copy of the files as the URL changed.

See: web/core/lib/Drupal/Core/Asset/JsCollectionRenderer.php:62

The other option is to explicitly set the module's version on these lines and keep track of it when the version number changes/the asset is updated.

🐛 Bug report

Status

Active

Version

3.0

Component

Code

Created by

🇮🇳India prem suthar Ahemdabad- Gujrat , Jodhpur - Rajsthan

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Merge Requests

!276Remove VERSION from libraries.yml
Open
🇮🇳India prem suthar
updated 8 days ago

Comments & Activities

Issue created by @prem suthar
Comment 8 days ago →
nidhish
Merge request !276Remove VERSION from libraries.yml File. → (Open) created by prem suthar
Pipeline finished with Success
8 days ago
Total: 713s
#402551
Comment 8 days ago →
🇮🇳India prem suthar Ahemdabad- Gujrat , Jodhpur - Rajsthan
Comment 8 days ago →
🇧🇪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.
Comment 8 days ago →
🇮🇳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!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024