Incorrect hash for dynamic CSS files not using contenthash,
See original GitHub issueHi, when using prerender-loader
in conjunction with mini-css-extract-plugin
there is an error loading CSS imported by dynamic-chunks
when the hashing strategy is different from contenthash
for that css file.
In that case, prerender-loader
outputs a link pointing to a CSS file with a different hash.
Note that this doesn’t apply to JS files nor to CSS files imported by the main (entrypoint) chunk.
A full reproduction is in https://github.com/isidrok/prerender-loader-reprod, look at the readme for more information.
The original discussion is in GoogleChromeLabs/critters#7
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
webpack not adding [contenthash] properly to my .js files
Try to use [hash] instead of [contentHash ] . This worked for me.
Read more >Adding Hashes to Filenames - SurviveJS
A content hash is derived based on the chunk content. If you are using MiniCssExtractPlugin , you should use [contenthash] as well. This...
Read more >Bust That Cache Through A Content Hash - Alain Schlesser
The problem with this approach is that depending on what servers the visitor's connection is passing through, the assets will not be cached...
Read more >What they don't tell you about webpack dynamic imports
So, if you're starting to use dynamic chunks, open the "Sources" tab in DevTools to see if there are hashes in the dynamic...
Read more >Production - Parcel
You can also disable content hashing using the --no-content-hash CLI flag. Note that the name will still include a hash, but it will...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This should be fixed now as long as you upgrade to the latest (0.4.4) mini-css-extract-plugin!
That makes sense. Perhaps it’d be worth having the plugin warn when
[hash]
is used.