-
Notifications
You must be signed in to change notification settings - Fork 73
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
Chunkhash in filename still differs #7
Comments
(This may totally be an issue in |
I just created this issue: webpack/webpack#1315. Has an example as well: https://github.com/kevinrenskers/chunkhash-problem. |
Cool - glad to see I'm not alone. I'll follow that thread and this one to see if anyone has relevant knowledge towards cause or a fix. |
+1 |
Is this still a pain point for others? I found a solution that works for my use-case. I will raise a PR so @diurnalist and others can critique. But tomorrow after sleep. |
So at startup Noting that The problem is that I am proposing a monkey-patch of You can install from bholloway/chunk-manifest-webpack-plugin and I have PR #9. Additionally, let me know if this is relevant to webpack/webpack#1315. |
This issue should be closed based on the response to the question I posed. Essentially if you use webpack-md5-hash plugin the problem goes away. Refer to webpack/webpack#1315 for a full solution. |
Using the md5hash plugin still having an issue with naming of the chunks; PR #11 |
knock knock |
If a plugin requires another dependency to work, then this should be mentioned in the readme. soundcloud#7
If a plugin requires another dependency to work, then this should be mentioned in the readme. soundcloud#7
If a plugin requires another dependency to work, then this should be mentioned in the readme. soundcloud#7
This plugin works great, thanks for writing it.
I'm experiencing an issue where the contents of a commons chunk are now identical across compiles where the only code changed is not in the commons chunk, but the
chunkHash
webpack outputs for the commons chunk filename is still different.Anyone else ever run into this?
The text was updated successfully, but these errors were encountered: