-
-
Notifications
You must be signed in to change notification settings - Fork 384
contenthash generates same filename for different contents #454
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
Comments
Please create reproducible test repo |
@evilebottnawi updated description with a minimal reproducible repo and steps |
Send a fix, thanks for the PR |
@evilebottnawi any update? We are getting this issue again |
@zlk89 no right now, but will be fixed in near future |
@alexander-akait looks like the issue is still existed. I have bumped the repo to latest webpack (v5.10) and mini css extract plugin (v1.3.2) |
@zlk89 Yep, a lot of work, but it in my TODO, sorry 😞 |
^ bump, this bug essentially prevents us from utilizing long term cache on all css generated by this plugin |
verified the bug has been fixed |
Expected Behavior
Should generate different filename when content is changed.
Actual Behavior
Same filename was generated when content is updated.
How Do We Reproduce?
https://github.com/zlk89/webpack-css-contenthash-diff
yarn
to install packagesyarn build
dist
folder, you will find two css files with same content hash, while content is different.Basically contenthash is same, when import statement order is different:
The text was updated successfully, but these errors were encountered: