ServiceWorker fetch failed (ERR_NAME_NOT_RESOLVED)

[trogper]

Installing serviceworker using following code fails with ERR_NAME_NOT_RESOLVED
I am able to load sw.js file using ajax and via script tag just fine

navigator.serviceWorker.register('sw.js').then(function(registration) {
  console.log('ServiceWorker registration successful with scope: ', registration.scope);
}, function(err) {
  console.log('ServiceWorker registration failed: ', err);
});

The result is

An unknown error occurred when fetching the script.
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
ServiceWorker registration failed:  TypeError: Failed to register a ServiceWorker: An unknown error occurred when fetching the script.

[pavelfeldman]

I can look into fixing this, but you would pretty much never want to use ServiceWorker in combination with Carlo. What is your use case?

When running Carlo, your Node application is a sort of a ServiceWorker on steroids itself. I can expose fetch interception from Puppeteer so that it looked similar to ServiceWorker, but given that you already have RPC between the two, you would rarely need it.

[trogper]

Rich notifications, since It's only possible to create them from ServiceWorker.
Windows 10 requires an app to "be installed" and provide it's appID to create them.

[pavelfeldman]

Do you think something like node-notifier could do the job?

[trogper]

I have tried it, It also requires the appID

[pavelfeldman]

Got it, thanks for confirming. We would want to make sure any web content loads in Carlo, so your SW request stands as a bug report.

[jamesb3ll]

Web Push support (GCM) from Service Worker pushManager would be great as electron doesn't support it: electron/electron#6697