Webpack: A bad HTTP response code (404) was received when fetching the script.

[gazpachu]

Any idea of what's that??

[LinusBorg]

It seems you are using a service worker?

That's not part of this template, so in don't see how this repository has anything to do with it.

[gazpachu]

Yes, this was probably a previous app running on the same port. Thx

[Nayir]

@gazpachu any idea for solve this ? How to kill the previous app service-worker ? Thanks

[gazpachu]

@Nayir somehow it stopped appearing. I'm not sure how it happened.

[gazpachu]

@LinusBorg @Nayir it actually keeps appearing, so it's really something that comes from this package

[davidmoshal]

I have this problem too. How does one kill it?

[Nayir]

Someone is using UIkit 3.0 ? Maybe the error comes from UIkit and not Vuejs.

[davidmoshal]

You kill it by unsubscribing the service worker from the local host port

[LinusBorg]

@davidmoshal I still have no idea where this service worker is coming from. Have you found out more?

[Nayir]

I run this is the console of my navigator (Chrome), and no error message anymore :

navigator.serviceWorker.getRegistrations().then(function(registrations) { for(let registration of registrations) { registration.unregister() } })

[Nayir]

@LinusBorg I think it's coming from Vue-Hacker-News example project. And then when you run a new webpack vue-cli project, the service worker is still running for this one.

[LinusBorg]

Ah that would make sense :)

[wangdahoo]

@Nayir it works for me. thanks.

[LinusBorg]

I'm sorry but this repository has nothing to do with angular or OneSignal, so i have no idea why you are asking here.

The only tipp I can give you is to check your chrome devtools under the "Application" tab when on localhost, and kill all service workers that may still be running.

[satyaram413]

If you're using a local repository then while specifying the URL or path of your file, don't specify the absolute path instead give an absolute path, for example, is the correct way to do it, so this isn't the correct way to do it. Well, this worked out for me, hope force may be with you.

[evenfrost]

To remove previous service worker along with other cache, if using Chrome, open DevTools and long press on 'Refresh button' ↻, then select 'Empty Cache and Hard Reload' option.

[ignacio68]

Chrome=>Dev Tools=>Application=>Service Workers=>Update on reload (selected)

[gangsthub]

@ignacio68 that made it! Thanks

[migueldeguzman]

This error also occured in a reactjs project. same code above resolved it!

[migueldeguzman]

I run this is the console of my navigator (Chrome), and no error message anymore :

navigator.serviceWorker.getRegistrations().then(function(registrations) { for(let registration of registrations) { registration.unregister() } })

thanks for this dude!

[LuisEspinosaB]

I run this is the console of my navigator (Chrome), and no error message anymore :
navigator.serviceWorker.getRegistrations().then(function(registrations) { for(let registration of registrations) { registration.unregister() } })

thanks for this dude!

It really works! Thank you!

[lilitatd]

navigator.serviceWorker.getRegistrations().then(function(registrations) { for(let registration of registrations) { registration.unregister() } })

It works for me. Thanks!

[blogxkomo]

navigator.serviceWorker.getRegistrations().then(function(registrations) { for(let registration of registrations) { registration.unregister() } })

thanks it's work for me :)

[sarink]

This happens when a previous app on the same url did utilize a service worker.

To fix:
Chrome - devtools - Application - Clear storage - check Unregister Service Worker - then click Clear site data

[timeworn]

I run this is the console of my navigator (Chrome), and no error message anymore :

navigator.serviceWorker.getRegistrations().then(function(registrations) { for(let registration of registrations) { registration.unregister() } })

hi friend, let me know more exactly , where can i use this command ?

[AndrewBogdanovTSS]

@timeworn I guess you can just paste it in your console window of Chrome dev tools. But for me that command, although executed, made no difference. Error still appears

[timeworn]

I run this is the console of my navigator (Chrome), and no error message anymore :

navigator.serviceWorker.getRegistrations().then(function(registrations) { for(let registration of registrations) { registration.unregister() } })

Hi friend, please let me know with screenshot more exactly, thanks

[stoneshower]

[quangtuyendev]

I have this problem too. How does one kill it?
Thanks all

[x3sammy]

Any idea of what's that??

for me, it was finding firebase-messaging-sw.js in my root dir, but i've created it inside the /var/www/html/test/ ........ just paste it
sw.js file in root dir -> /var/www/html

this worked for me ::)