-
Notifications
You must be signed in to change notification settings - Fork 21
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 of produced assets changes even if source stays the same #7
Comments
I only changed application code. |
The vendor file differs only in following:
|
Can you please provide sample project where this can be reproduced? I'll try to debug it |
It' the default one you provided in the readme: Please change v2 to v3 in index.js, and notice that vendor contents and chunkhash changes upon rebuild |
The comment in vendor bundle says:
Shouldn't it be the other way around? The index chunk should be entry chunk and load vendor one.. |
+1, the hash of seldom changed vendor.js should not change every compilation |
Related thread: webpack/webpack#1315 The main idea there is to extract |
👍 |
Sorry, I don't have much free time now, so I can't quickly fix this issue, but I will be able to accept PR if someone will make one. |
so should we separate the manifest module to a standalone chunk as built-in behavior of this plugin or just an option? |
1. move the bucketChunks management out of the entry chunk loop which makes more sense. 2. create a manifest chunk to act as the only entry chunk. see discussion in BohdanTkachenko#7 ps: improve example's html script entries
@e-cloud did a pull request that seems to be fixing this issue. Closing this issue for now. Please re-open it if there still any problems |
Hey,
I tried to use your plugin, but the chunkhash of my vendor chunk changes even if I don't modify any of my vendor dependencies.. Here is my configuration:
Any tips?
The text was updated successfully, but these errors were encountered: