You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The resulting filename of chunks contains content hash (which is, the pretty common configuration) and because of that, chunks cannot be compared between builds. names collection is empty, so files is used as a fallback which is not the best idea in this case.
The text was updated successfully, but these errors were encountered:
The best idea that comes to my mind now is to extend the comparison algorithm, so it's like this:
check the names collection
when there is no match, check files collection
when there is no match, check the identifier of the entry points (the first one? all? any?)
when there is no match, rely on the order
There is a risk for a false-positive match, though, especially when chunks are added/removed/reordered. react-dev-utils does it by simply removing anything that looks like hash from the filename. Simple, but works in most cases, maybe that's the way?
Load these two stat files to see the issue:
Archive.zip
The resulting filename of chunks contains content hash (which is, the pretty common configuration) and because of that, chunks cannot be compared between builds.
names
collection is empty, sofiles
is used as a fallback which is not the best idea in this case.The text was updated successfully, but these errors were encountered: