You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CSS should be minified in build time or, in lack of a proper build system, deploy time. It does not make sense to have CSS minified on-demand when it won't change on-demand.
The minified CSS' URL may be style.min.css?md5={md5 in config}.
What about keeping old versions?
If the new version is MD5=123456, and a user requests MD5=000000, they will receive the new version since it's the only one the server can serve.
What if the HTML is outdated but a new CSS is received? It would be dangerous if the new CSS works only with new HTML, but the case is unusual.
When is the CSS' md5 updated? In every deploy means that even if it was not changed the users will renew it. If it's in build time, we could detect whether CSS has changed, but that's kind of magic. If it's in deploy time, we can have a checkbox in the deploy script that will re-minify the CSS and update the config.
The text was updated successfully, but these errors were encountered:
CSS should be minified in build time or, in lack of a proper build system, deploy time. It does not make sense to have CSS minified on-demand when it won't change on-demand.
The minified CSS' URL may be style.min.css?md5={md5 in config}.
What about keeping old versions?
When is the CSS' md5 updated? In every deploy means that even if it was not changed the users will renew it. If it's in build time, we could detect whether CSS has changed, but that's kind of magic. If it's in deploy time, we can have a checkbox in the deploy script that will re-minify the CSS and update the config.
The text was updated successfully, but these errors were encountered: