- Issue created by @dieterholvoet
- Status changed to Needs review
6 months ago 8:29am 15 July 2024 - First commit to issue fork.
- Status changed to Fixed
6 months ago 1:11pm 28 July 2024 - Status changed to Fixed
6 months ago 1:25pm 28 July 2024
I noticed changes to JS and CSS aren't always coming through on production environments.
Update some JS or CSS in the module. Deploy these changes to an environment where asset aggregation is enabled.
Remove versions from the library definitions, or make sure to always update them when changing something in the library files.
Taken from this change record → :
Aggregate filenames are now based on the library definition instead of the contents of the file. However if a library does not have a version, the contents of the file will be additionally used to make up part of the hash. This allows custom modules and themes to invalidate browser and edge caches without having to increment their version each deployment.
Fixed
1.2
Code