Add support for dev-server ? about serviceworker-webpack-plugin HOT 3 CLOSED

It should be working. Might be linked to a wrong configuration of the plugin. Does that work in production?

from serviceworker-webpack-plugin.

I'm having the same issue, [Failed to register a ServiceWorker: A bad HTTP response code (404) was received when fetching the script.]. I'm currently investigating my webpack config

Edit: It's almost certainly a webpack issue in that /sw.js is not resolving to the service worker file. Somehow webpack needs to be told to serve that js file/route.

Edit: I can make some parts work by manually serving the sw.js file. The two separate ways I achieved this were:

Adding the following to webpack.config devServer object:

    setup: app => {
      app.use('/', express.static(path.join(__dirname, 'src')));
    }

however, this shares far more than intended.

Secondly I tried using the webpack public folder. I moved the sw.js file into the public folder. This made the file serve properly without oversharing. However, this does not transpile the sw.js file.
After manual transpilation it throws errors that global is not defined, which makes me think it's not linked in properly with the plugin.

What is the 'right' way to serve this js file, but without affecting/sharing the rest of my JS files?

Edit:
I think I fixed this. It turned out that all I had to do was add a publicPath property since my webpack config outputs to '/assets/'

    new ServiceWorkerWebpackPlugin({
      entry: path.join(__dirname, 'src/service-worker.js'),
      publicPath: '/assets/'
    }),

from serviceworker-webpack-plugin.

@thehig Thanks for letting us know! I'm going to improve the docs a bit.

from serviceworker-webpack-plugin.