-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Put a cachebuster in the names of CSS and JS files #2515
Conversation
This means that clients can do better caching of assets, as it will mean we are no longer reliant on etags to ensure that clients get a fresh version. We inhibit the cachebuster for `npm start`, so that we don't get millions of copies of the bundles on dev boxes.
dcaf87c
to
6396c60
Compare
|
||
new HtmlWebpackPlugin({ | ||
template: './src/vector/index.html', | ||
inject: false, // we inject the links ourselves via the template |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because HtmlWebpackPlugin wants to put the script tags either in or at the end of , and I was a bit scared about moving it.
Otherwise lgtm |
(please don't merge this to develop yet) |
Looks like the cachebuster stuff in element-hq/element-web#2515 broke room tinting. Add a fix, along with some ranting.
This means that clients can do better caching of assets, as it will mean we are
no longer reliant on etags to ensure that clients get a fresh version.
We inhibit the cachebuster for
npm start
, so that we don't get millions ofcopies of the bundles on dev boxes.