Kaziu
Posted on April 15, 2022
There was like this conversation
š©āš» š»š³ - my friend who lives in Vietnam
šØāš šµš± - me, lives in Poland
š©āš» š»š³ I fixed CSS and it was good in my local environment,
but in test environment(AWS) doesn't change anything
šØāš šµš± aha
š©āš» š»š³ could you check it on your PC?
šØāš šµš± sure .... tadaaam css is changed on my PC
š©āš» š»š³ what?? yeah exactly...
šØāš šµš± Have you tried deleting cache?
š©āš» š»š³ Yeah, I've tried it at first
šØāš šµš± hmm... could you try to use incognito chrome?
š©āš» š»š³ Just moment ... it turns out same result...
šØāš šµš± on incognito chrome as well ??? Maybe CDN cache??
š©āš» š»š³ How can I check it ?
šØāš šµš± chrome devtool > Network > Headers > X-cache
I see I get css file from CDN(AWS cloudfront)
šØāš šµš± and age means the time when this file was created.
so I get file which is created 118 seconds ago on CDN
šØāš šµš± How is it on your PC?
š©āš» š»š³ age is 279313, so almost 3days ago ! this is the reason !!
2 days later...
file name was like main%5BchunkHash%%5D.css, but it should have be like 7530r9w4j0fef0we.css (without "chunckHash")
it means version of css file.
the reason why css file name was not property was mini-css-extrace-plugin version.
after my friend updated version, everything was ok š
according to AWS doc, if css name is not included version identifier, cache doesn't update.
š šŖ š
š©
Kaziu
Posted on April 15, 2022
Join Our Newsletter. No Spam, Only the good stuff.
Sign up to receive the latest update from our blog.