Bot releases are visible (Hide)
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
6c3e789
]:
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
6c3e789
Thanks @DuCanhGH! - feat(precaching.PrecacheFallbackPlugin): renamed fallbackURL
, added support for a matcher
fallbackURL
has been renamed to fallbackUrls
, which should now be an array of strings or PrecacheFallbackEntry
's.
PrecacheFallbackEntry
is an interface that requires a fallback URL and a matcher, which is used to check whether the current fallback entry can be used for a request.
To migrate:
new PrecacheFallbackPlugin({
fallbackURL: "/~offline",
});
new PrecacheFallbackPlugin({
fallbackUrls: ["/~offline"],
});
// Or
new PrecacheFallbackPlugin({
fallbackUrls: [
{
url: "/~offline",
matcher({ request }) {
return request.destination === "document";
},
},
],
});
With this change, @serwist/sw.fallbacks
now also uses PrecacheFallbackPlugin
. This means that FallbackEntry.cacheMatchOptions
has been removed, for PrecacheController.matchPrecache
doesn't support a custom matchOptions
. This option is most likely not needed anyway.
To migrate:
fallbacks({
entries: [
{
url: "/~offline",
revision,
matcher({ request }) {
return request.destination === "document";
},
cacheMatchOptions: { ignoreSearch: true },
},
],
runtimeCaching,
});
fallbacks({
entries: [
{
url: "/~offline",
revision,
matcher({ request }) {
return request.destination === "document";
},
},
],
runtimeCaching,
});
6c3e789
]:
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
6c3e789
]:
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
6c3e789
Thanks @DuCanhGH! - feat(precaching.PrecacheFallbackPlugin): renamed fallbackURL
, added support for a matcher
fallbackURL
has been renamed to fallbackUrls
, which should now be an array of strings or PrecacheFallbackEntry
's.
PrecacheFallbackEntry
is an interface that requires a fallback URL and a matcher, which is used to check whether the current fallback entry can be used for a request.
To migrate:
new PrecacheFallbackPlugin({
fallbackURL: "/~offline",
});
new PrecacheFallbackPlugin({
fallbackUrls: ["/~offline"],
});
// Or
new PrecacheFallbackPlugin({
fallbackUrls: [
{
url: "/~offline",
matcher({ request }) {
return request.destination === "document";
},
},
],
});
With this change, @serwist/sw.fallbacks
now also uses PrecacheFallbackPlugin
. This means that FallbackEntry.cacheMatchOptions
has been removed, for PrecacheController.matchPrecache
doesn't support a custom matchOptions
. This option is most likely not needed anyway.
To migrate:
fallbacks({
entries: [
{
url: "/~offline",
revision,
matcher({ request }) {
return request.destination === "document";
},
cacheMatchOptions: { ignoreSearch: true },
},
],
runtimeCaching,
});
fallbacks({
entries: [
{
url: "/~offline",
revision,
matcher({ request }) {
return request.destination === "document";
},
},
],
runtimeCaching,
});
Published by github-actions[bot] 8 months ago
7524712
Thanks @DuCanhGH! - chore(next): changed defaultCache
's "next-data"
's handler to NetworkFirst
Using StaleWhileRevalidate
seems to affect getServerSideProps
. See https://github.com/serwist/serwist/issues/74 for more details.
There's nothing to be done on your side.
6c3e789
]:
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
Published by github-actions[bot] 8 months ago
6c3e789
]: