| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| workbox-v5.0.0-beta.1.zip | 2019-10-01 | 361.5 kB | |
| workbox-v5.0.0-beta.1.tar.gz | 2019-10-01 | 296.9 kB | |
| README.md | 2019-10-01 | 2.0 kB | |
| Workbox v5.0.0-beta.1 source code.tar.gz | 2019-10-01 | 729.1 kB | |
| Workbox v5.0.0-beta.1 source code.zip | 2019-10-01 | 1.1 MB | |
| Totals: 5 Items | 2.5 MB | 0 | |
The latest beta release of Workbox v5 includes the following developer-visible changes, in addition to all the changes from the previous pre-release.
Installation of the latest pre-release version
We are using the next tag in npm for the current pre-release version. To install a given module use, e.g., npm install --save-dev workbox-webpack-plugin@next.
🐛 What's Fixed?
TypeScript
- Various type annotations have been updated for accuracy. [#2200, [#2208]]
All build tools
- If the
swSrcfile has an associated sourcemap, we now update that to account for the injected manifest. [#2239]
workbox-build
-
Fixed a bug that could lead to the output directory being prepended twice when writing the service worker to disk. [#2223]
-
Make sure that all
swSrcandswDestfiles are left out of the generated precache manifest. [#2232]
workbox-broadcast-update
- Added a check to wait for the resulting client to load on navigation requests before broadcasting any update messages. [#2210]
workbox-precaching
- Instead of adding the
__WB_REVISION__query parameter to outgoing network requests that should be cache-busted, explicitly set thecachemode to'reload'if needed. When cache-busting is not needed, setcacheto'default'. [#2222]
workbox-range-requests
- Fixed a bug causing an invalid
206 Partial Contentresponse to be used when the incoming request usedRange: bytes=0-. [#2237]
workbox-webpack-plugin
- Fixed an edge case that could lead to build errors when other plugins generate assets. [#2219]
workbox-window
- The
messageevent listener is now added earlier, inside of the constructor rather than theregister()method. [#2211]
Thanks
Special thanks to @lukas2005 for their bug reports, and @azizhk for their contributions that went into this release!