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
The javascript chunking configuration currently uses [name]_[chunkhash].js as filename, which makes it easy to permanently cache the chunk: if its contents change its name changes as well.
Currently we have a single prerender.css. What would it take to do the same thing with css chunks?
oh wow, exactly my thoughts after reading #139. Yeah, let's just chunkhash the css file. Although fair warning, I'm thinking about doing away with stylesheets in the future, so I'm not sure if it's worth the effort. For future reference though:
add in a chunkhash on the filename
add the AssetsPlugin to the webpack server config, set it to serve a new file, eg serverAssets.json
grab the css from serverAssets & inject it into the HTML (currently it's hardcoded to prerender.css)
The javascript chunking configuration currently uses
[name]_[chunkhash].js
as filename, which makes it easy to permanently cache the chunk: if its contents change its name changes as well.Currently we have a single
prerender.css
. What would it take to do the same thing with css chunks?followup to #139
The text was updated successfully, but these errors were encountered: