Changes to JS and CSS aren't always coming through on production environments

Created on 15 July 2024, 3 months ago

Updated 28 July 2024, 3 months ago

Problem/Motivation

I noticed changes to JS and CSS aren't always coming through on production environments.

Steps to reproduce

Update some JS or CSS in the module. Deploy these changes to an environment where asset aggregation is enabled.

Proposed resolution

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.

🐛 Bug report

Status

Fixed

Version

1.2

Component

Code

Created by

🇧🇪Belgium dieterholvoet Brussels

Live updates comments and jobs are added and updated live.

Merge Requests

!101Changes to JS and CSS aren't always coming through on production environments
Merged
🇧🇪Belgium dieterholvoet
updated 3 months ago

Comments & Activities

Issue created by @dieterholvoet
Merge request !101Remove versions from library definitions → (Merged) created by dieterholvoet
Status changed to Needs review 3 months ago8:29am 15 July 2024
Comment 3 months ago →
🇧🇪Belgium dieterholvoet Brussels
Pipeline finished with Success
3 months ago
Total: 327s
#224498
First commit to issue fork.
Status changed to Fixed 3 months ago1:11pm 28 July 2024
Comment 3 months ago →
🇪🇸Spain gxleano Cáceres
It will be included on release 1.2.19
Status changed to Fixed 3 months ago1:25pm 28 July 2024
Comment 3 months ago →
🇪🇸Spain gxleano Cáceres

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024