- Issue created by @hosterholz
- Merge request !23Issue #3542233 by hosterholz: Do not use Drupal Core's version for libraries → (Open) created by hosterholz
When updating dropzonejs but not drupal/core, the JavaScript cache-busting parameter remains the same (e.g. ?v=10.4.8). When updating drupal/core but not dropzonejs, the JavaScript cache-busting parameter changes.
LibraryDiscoveryParser applies the Drupal version to every library that uses version: VERSION. It does not use the modules version.
See the note on Adding assets (CSS, JS) to a Drupal module via *.libraries.yml → :
Starting from Drupal 10.1.2, the version information within a library definition plays a critical role in generating a unique hash for aggregated files. Consequently, it is imperative that the "version" in a library definition is updated whenever a referenced CSS/JS file undergoes changes.
Alternatively, if the version is omitted, the prior behavior will apply, where the content of referenced CSS/JS files is utilized in the hash.
Incorrect usage of version information could lead to browser and edge cache invalidation issues.
See this update → on the related changelog → .
First case
$config['system.performance']['js']['preprocess'] = FALSE;<script src="/modules/contrib/dropzonejs/js/dropzone.integration.js?v=10.4.8"></script><script src="/modules/contrib/dropzonejs/js/dropzone.integration.js?v=10.4.8"></script>Second case
$config['system.performance']['js']['preprocess'] = FALSE;<script src="/modules/contrib/dropzonejs/js/dropzone.integration.js?v=10.4.7"></script><script src="/modules/contrib/dropzonejs/js/dropzone.integration.js?v=10.4.8"></script>Remove version: VERSION from dropzonejs.libraries.yml
Active
2.0
Code