This feature of Netlify is one of my favorite features. Suppose you are developing a website and have changed a resource, such as CSS, JavaScript, or image files. You know, just like we do everyday. On Netlify, you don't need to consider how this will affect deployment, browser, and cache. Netlify will handle all of this for you.
Netlify calls this instant cache failure and is part of Netlify's "rocket fuel."
In all the non-Netlify sites I have to consider this (hate). If you look at the source code of this website, you will see a stylesheet link like this:
<code><link href="https://css-tricks.com/wp-content/themes/CSS-Tricks-17/style.css?cache_bust=1594590986788" rel="stylesheet"></code>
Have you seen the ?cache_bust=
part at the end? These are just meaningless characters that I manually add to the URL (based on Date()
call), so that when I push changes to the file, it breaks the CDN and the user's browser cache at the same time, and they get the new file. If I don't do this, my changes will not be seen unless all caches expire or are manually deleted by the user, which...sucks. I may be fixing the error! Or release new features! This is especially bad because the CSS may be used in conjunction with some HTML that is less aggressive in caching and may cause the HTML to mismatch with the expected CSS.
Some of the sites I'm involved in need of me changing that cache manually as I'm too lazy to automate it. Normally, I automate it. I recently shared my handwritten Gulpfile, part of which handles this cache clearance. Writing, maintaining, and using it during development requires effort. You can even read the comments for the post and see the strategies others do the same, which are different from mine. Everyone is doing cache clearance.
This is not necessary on Netlify.
Likewise, you change the resource, upload it, and Netlify will know it has changed and perform all cache clearing operations for you. So your stylesheet can be linked like this:
<code><link href="%E6%97%A0%E9%9C%80%E6%8B%85%E5%BF%83.css" rel="stylesheet"></code>
The above is the detailed content of Netlify Does Cache Invalidation For You. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

No,CSSdoesnothavetobeinlowercase.However,usinglowercaseisrecommendedfor:1)Consistencyandreadability,2)Avoidingerrorsinrelatedtechnologies,3)Potentialperformancebenefits,and4)Improvedcollaborationwithinteams.

CSSismostlycase-insensitive,butURLsandfontfamilynamesarecase-sensitive.1)Propertiesandvalueslikecolor:red;arenotcase-sensitive.2)URLsmustmatchtheserver'scase,e.g.,/images/Logo.png.3)Fontfamilynameslike'OpenSans'mustbeexact.

Autoprefixer is a tool that automatically adds vendor prefixes to CSS attributes based on the target browser scope. 1. It solves the problem of manually maintaining prefixes with errors; 2. Work through the PostCSS plug-in form, parse CSS, analyze attributes that need to be prefixed, and generate code according to configuration; 3. The usage steps include installing plug-ins, setting browserslist, and enabling them in the build process; 4. Notes include not manually adding prefixes, keeping configuration updates, prefixes not all attributes, and it is recommended to use them with the preprocessor.

CSScounterscanautomaticallynumbersectionsandlists.1)Usecounter-resettoinitialize,counter-incrementtoincrease,andcounter()orcounters()todisplayvalues.2)CombinewithJavaScriptfordynamiccontenttoensureaccurateupdates.

In CSS, selector and attribute names are case-sensitive, while values, named colors, URLs, and custom attributes are case-sensitive. 1. The selector and attribute names are case-insensitive, such as background-color and background-Color are the same. 2. The hexadecimal color in the value is case-sensitive, but the named color is case-sensitive, such as red and Red is invalid. 3. URLs are case sensitive and may cause file loading problems. 4. Custom properties (variables) are case sensitive, and you need to pay attention to the consistency of case when using them.

CSSselectorsandpropertynamesarecase-insensitive,whilevaluescanbecase-sensitivedependingoncontext.1)Selectorslike'div'and'DIV'areequivalent.2)Propertiessuchas'background-color'and'BACKGROUND-COLOR'aretreatedthesame.3)Valueslikecolornamesarecase-insens
