-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Add fingerprint to compiled css/js files #439
Comments
Hi @tooooolong! How would one know whether a fingerprint should be used? Some sort of configuration option? |
maybe something like this。 this is a plugin for Webpack, it will add a hash to the static file name automatically. |
This is a good idea 👍 I think fingerprinting can be turned on by default. It's also necessary in PWAs because they cache the content via paths. This only needs to be done during the build phase. The |
is anyone taking this @yangshun? I can work on this in the coming weeks |
Sure thing, it's yours! I've added an "issue-claimed" label so that others will know not to start work on the issue. If you change your mind about the issue, no worries! Just let me know so that I can remove the label and free it up for someone else to claim. I'll check in with you periodically so that we can keep the task updated with the progress. |
Awesome 😎 |
Implemented in v2 |
Case we have CDN front of our website, So main.css can not update automaticly.
Now, the css tag is:
I think it should add fingerprint to static files.
Something like this:
The text was updated successfully, but these errors were encountered: