v0.22.2: Important bug fixes to versioning & caching
This bug fix release includes several important changes that fix some versioning bugs and improve caching.
To upgrade: yarn upgrade
Changes: v0.22.1..v0.22.2
Highlights:
-
Fix an issue where JavaScript files might change, but their versioning hash filename would NOT change - causing problems where users would use out-of-date cached assets, instead of dowloading the new ones. This works by, internall, using the names of modules in compiled files. This bug only affected users using
enableSingleRuntimeChunk()
- #462 -
Fixed a bug where certain content changes to a JavaScript file would not cause the versioning hash to update. This relates to the first fixed bug. Due to the changing in how hashing works, all JavaScript files will have a new hash the first time after upgrading - #463
-
Fixed a bug with
splitEntryChunks()
where some filenames and contents of files would change unnecessarily. This did not cause any bad behavior, but meant that users would unnecessarily download new assets, that really didn't need to change between builds. As a result, you'll notice that instead of split chunks named something likevendors~abc123.js
, inproduction
, they will be called0.js
or some other integer. This makes no functional difference - #462