Open vincenthend opened 1 year ago
Since foo.js keeps changing on every build, thedebugId generated for main.js is affected
Can you explain why changing foo.js affects the hash of main.js?
But in general you're probably right that we should use the content hash instead.
Can you explain why changing foo.js affects the hash of main.js?
Hmm, if I'm debugging it correctly, the cause for my case is due to chunk.hash
for entry files seems to be generated using the child compilation
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
Environment
@sentry/webpack-plugin@2.7.0
Steps to Reproduce
other_entry.js
is usingfoo.js
main.js
is usingbar.js
[id].[contentHash].js
for caching purposesfoo.js
keeps changing on every build, thedebugId
generated formain.js
is affecteddebugId
formain.js
changed changing the finalcontentHash
and breaking the cache behaviourdebugId
forbar.js
remains constantApparently this happened due to the use of
hash
for generatingdebugId
Expected Result
debugID
onmain.js
should remain constant since the real file content doesn't changeActual Result
debugID
formain.js
changed although the real content of the file doesn't change.Suggestion
Probably good if we can have it generated based on
contentHash
instead ofhash