Use service worker on localhost

[Everettss]

Current Build Setup serve from http://localhost:8080/ but in entry-server.js is

// service worker
if ('https:' === location.protocol && navigator.serviceWorker) {
  navigator.serviceWorker.register('/service-worker.js')
}

There is problem with 'https:' === location.protocol on localhost.
Is this check really needed? It introduce unnecessary complexity of need serving from https on localhost. If you remove this check and run on http not on localhost it will simple throw an error - for me this should be expected behaviour (developer will easily spot this problem) .

[JounQin]

Service workers only run over HTTPS, for security reasons.

[Everettss]

And on localhost without HTTPS, for development purposes.

[JounQin]

980ca32#r26021186

It seems browser will ignore localhost or 127.0.0.1 without https, so maybe we can add some check for that.

I add this code because we are only using service worker on production here, which will not only run on localhost.

Maybe check like following:

process.env.NODE_ENV === 'production' && ('https:' === location.protocol || ['localhost', '127.0.0.1'].indexOf(location.host) !== -1) && navigator.serviceWorker

[Everettss]

This one is working:

// service worker
if (
  process.env.NODE_ENV === 'production' &&
  ('https:' === location.protocol || location.host.match(/(localhost|127.0.0.1)/)) &&
  navigator.serviceWorker
) {
  navigator.serviceWorker.register('/service-worker.js');
}

but what is the purposes of process.env.NODE_ENV === 'production'? It looks like this NODE_ENV is in all builds set to production Why to stop people from debugging service worker in development environment?

Personally I think we over engineering this simple problem, just use the most popular option:

// service worker
if ('serviceWorker' in navigator) {
  navigator.serviceWorker.register('/service-worker.js');
}

[JounQin]

ServiceWorker is only enabled on production build.
https://github.com/vuejs/vue-hackernews-2.0/blob/master/build/webpack.client.config.js#L44

And, if user publishes this demo onto his own server without https support, it will breaks, right?

[Everettss]

It will not break it will throw an error that you try to register service worker on not secure domain. But the application will work fine. OK - lets not change this process.env.NODE_ENV === 'production' workflow. Just use this:

// service worker
if (
  process.env.NODE_ENV === 'production' &&
  ('https:' === location.protocol || location.host.match(/(localhost|127.0.0.1)/)) &&
  navigator.serviceWorker
) {
  navigator.serviceWorker.register('/service-worker.js');
}

[JounQin]

Yes, it will throw an error, and just seems to be a break to me, so why not check it and avoid an error?

[Everettss]

Because it shows developer that he is trying to publish site with service worker on not secure domain. It is his fault that he doesn't care about HTTPS. Let's not nurse him.

[rahul7p]

@Everettss @JounQin

I have added same in webpack.client.config.js file but still getting error like

Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker: The script has an unsupported MIME type ('text/html'). (messaging/failed-serviceworker-registration).

navigator.serviceWorker.register('firebase-messaging-sw.js')
.then((registration) => {
console.log('registration=>',registration);
Vue.prototype.$messaging.useServiceWorker(registration)
}).catch(err => {
console.log("here....")
console.log(err)
})

Will you please guide me?