How to handle releases with a service worker which uses API?
I have the following scenario:
- A web application with a service worker (workbox)
- An API which the web application consumes
How am I expected to handle the changes in the API in the web application? It's important to take into account the service-worker life cycle. The service-worker will continue to use the previous version until the web is reloaded, so an user could be consuming outdated API endpoints, or missing new required params.
Currently, what I am doing is reloading the page as soon as a new version is installed, but it seems it's not fully working and also it's not very optimal:
if ('serviceWorker' in navigator) {
navigator.serviceWorker.register('/sw.js').then(function (registration) {
console.log('Service worker registered')
setInterval(() => {
console.log('Checking for updates');
registration.update();
}, 1000 * 60 * 60); // Checking for updates every hour
if (!navigator.serviceWorker.controller) { // New user with no service worker
return;
}
var preventDevToolsReloadLoop;
navigator.serviceWorker.addEventListener('controllerchange', function (event) { // This event is called when a new sw is installed
if (preventDevToolsReloadLoop) return; // Ensure refresh is only called once. This works around a bug in "force update on reload" in chrome tools.
preventDevToolsReloadLoop = true;
console.log('Controller loaded');
window.location.reload();
});
});
} else {
console.log('Service worker not activated')
}
sw.js looks like this:
importScripts('/js/workbox.4c4f5ca6.js')
workbox.precaching.precacheAndRoute([ /*Routes...*/ ]);
workbox.clientsClaim()
workbox.skipWaiting()
workbox.routing.registerRoute(new RegExp('/js/.*'),
workbox.strategies.cacheFirst({}), 'GET')
workbox.routing.registerRoute(new RegExp('/.*'),
workbox.strategies.networkFirst({}), 'GET')
service-worker
workbox asked Nov 15 '18 at 13:16
GuitoGuito
6331618
add a comment |
I have the following scenario:
- A web application with a service worker (workbox)
- An API which the web application consumes
How am I expected to handle the changes in the API in the web application? It's important to take into account the service-worker life cycle. The service-worker will continue to use the previous version until the web is reloaded, so an user could be consuming outdated API endpoints, or missing new required params.
Currently, what I am doing is reloading the page as soon as a new version is installed, but it seems it's not fully working and also it's not very optimal:
if ('serviceWorker' in navigator) {
navigator.serviceWorker.register('/sw.js').then(function (registration) {
console.log('Service worker registered')
setInterval(() => {
console.log('Checking for updates');
registration.update();
}, 1000 * 60 * 60); // Checking for updates every hour
if (!navigator.serviceWorker.controller) { // New user with no service worker
return;
}
var preventDevToolsReloadLoop;
navigator.serviceWorker.addEventListener('controllerchange', function (event) { // This event is called when a new sw is installed
if (preventDevToolsReloadLoop) return; // Ensure refresh is only called once. This works around a bug in "force update on reload" in chrome tools.
preventDevToolsReloadLoop = true;
console.log('Controller loaded');
window.location.reload();
});
});
} else {
console.log('Service worker not activated')
}
sw.js looks like this:
importScripts('/js/workbox.4c4f5ca6.js')
workbox.precaching.precacheAndRoute([ /*Routes...*/ ]);
workbox.clientsClaim()
workbox.skipWaiting()
workbox.routing.registerRoute(new RegExp('/js/.*'),
workbox.strategies.cacheFirst({}), 'GET')
workbox.routing.registerRoute(new RegExp('/.*'),
workbox.strategies.networkFirst({}), 'GET')
service-worker
workbox asked Nov 15 '18 at 13:16
GuitoGuito
6331618
add a comment |
I have the following scenario:
- A web application with a service worker (workbox)
- An API which the web application consumes
How am I expected to handle the changes in the API in the web application? It's important to take into account the service-worker life cycle. The service-worker will continue to use the previous version until the web is reloaded, so an user could be consuming outdated API endpoints, or missing new required params.
Currently, what I am doing is reloading the page as soon as a new version is installed, but it seems it's not fully working and also it's not very optimal:
if ('serviceWorker' in navigator) {
navigator.serviceWorker.register('/sw.js').then(function (registration) {
console.log('Service worker registered')
setInterval(() => {
console.log('Checking for updates');
registration.update();
}, 1000 * 60 * 60); // Checking for updates every hour
if (!navigator.serviceWorker.controller) { // New user with no service worker
return;
}
var preventDevToolsReloadLoop;
navigator.serviceWorker.addEventListener('controllerchange', function (event) { // This event is called when a new sw is installed
if (preventDevToolsReloadLoop) return; // Ensure refresh is only called once. This works around a bug in "force update on reload" in chrome tools.
preventDevToolsReloadLoop = true;
console.log('Controller loaded');
window.location.reload();
});
});
} else {
console.log('Service worker not activated')
}
sw.js looks like this:
importScripts('/js/workbox.4c4f5ca6.js')
workbox.precaching.precacheAndRoute([ /*Routes...*/ ]);
workbox.clientsClaim()
workbox.skipWaiting()
workbox.routing.registerRoute(new RegExp('/js/.*'),
workbox.strategies.cacheFirst({}), 'GET')
workbox.routing.registerRoute(new RegExp('/.*'),
workbox.strategies.networkFirst({}), 'GET')
service-worker
workbox asked Nov 15 '18 at 13:16
GuitoGuito
6331618
I have the following scenario:
- A web application with a service worker (workbox)
- An API which the web application consumes
How am I expected to handle the changes in the API in the web application? It's important to take into account the service-worker life cycle. The service-worker will continue to use the previous version until the web is reloaded, so an user could be consuming outdated API endpoints, or missing new required params.
Currently, what I am doing is reloading the page as soon as a new version is installed, but it seems it's not fully working and also it's not very optimal:
if ('serviceWorker' in navigator) {
navigator.serviceWorker.register('/sw.js').then(function (registration) {
console.log('Service worker registered')
setInterval(() => {
console.log('Checking for updates');
registration.update();
}, 1000 * 60 * 60); // Checking for updates every hour
if (!navigator.serviceWorker.controller) { // New user with no service worker
return;
}
var preventDevToolsReloadLoop;
navigator.serviceWorker.addEventListener('controllerchange', function (event) { // This event is called when a new sw is installed
if (preventDevToolsReloadLoop) return; // Ensure refresh is only called once. This works around a bug in "force update on reload" in chrome tools.
preventDevToolsReloadLoop = true;
console.log('Controller loaded');
window.location.reload();
});
});
} else {
console.log('Service worker not activated')
}
sw.js looks like this:
importScripts('/js/workbox.4c4f5ca6.js')
workbox.precaching.precacheAndRoute([ /*Routes...*/ ]);
workbox.clientsClaim()
workbox.skipWaiting()
workbox.routing.registerRoute(new RegExp('/js/.*'),
workbox.strategies.cacheFirst({}), 'GET')
workbox.routing.registerRoute(new RegExp('/.*'),
workbox.strategies.networkFirst({}), 'GET')
service-worker
workbox service-worker
workbox asked Nov 15 '18 at 13:16
GuitoGuito
6331618
asked Nov 15 '18 at 13:16
GuitoGuito
6331618
asked Nov 15 '18 at 13:16
GuitoGuito
6331618
asked Nov 15 '18 at 13:16
GuitoGuito
6331618
asked Nov 15 '18 at 13:16
GuitoGuito
6331618
6331618
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53320358%2fhow-to-handle-releases-with-a-service-worker-which-uses-api%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53320358%2fhow-to-handle-releases-with-a-service-worker-which-uses-api%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
