'Crbug/1173575, non-JS module files deprecated. chromewebdata/(index)꞉5305:9:5551

I just created a new project and have run it for the first time using F5 or Ctrl + F5, the result in Chrome is:

The site can't be reached

err_connection_refused

I checked the option at the breakpoints for "Exceptions caught" and the following error is displayed.

Without "Exceptions caught" checked, the next error raised:

I tried to run "ng s -o" from the terminal and all work fine. The site is working well on port 4200, but I like to debug.

Here is my launch.json file, all by default:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "pwa-chrome",
            "request": "launch",
            "name": "Launch Chrome against localhost",
            "url": "http://localhost:4200",
            "webRoot": "${workspaceFolder}"
        }
    ]
}

Why is this happening?

Solution 1:^[1]

This misleading error message seemingly has nothing to do with Chrome or any deprecated functionality. It seems to occur whenever connectivity can't be established.

I got this while following the React tutorial for VS Code. In that tutorial you start by creating a template with npx then running it with npm start. That worked, and I could see that it was using http://localhost:3000 for the URL in the browser.

However when I changed the code as the tutorial requested and set a breakpoint to debug, I got the error in the OP's post, both with Chrome and with Edge.

VS Code was creating a default launch.json for debugging and populating it like this:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    "version": "0.2.0",
    "configurations": [
        {
            "type": "pwa-chrome",
            "request": "launch",
            "name": "Launch Chrome against localhost",
            "url": "http://localhost:8080",
            "webRoot": "${workspaceFolder}"
        }
    ]
}

And I needed to manually change the 8080 to 3000 which fixed the problem.

Key for me was configuring the breakpoint to catch the exception like the OP described (note - you can only configure that with the Debug icon selected in the far left icon menu). While the emitted error message is still the misleading "deprecated" one, there was a message that "the site can't be reached" which you can find if you dig a little - as shown here:

I imagine that practically any configuration issue that causes the connection to fail will cause this error. So firewall issues, missing host program, bad configuration (like mine), etc.

Solution 2:^[2]

I also had this issue and none of the solutions listed were helpful. However the problem was rather easy to solve.

Just go into the Network tab of the Chrome Developer Console. Be sure that the connection is on No throttling and not Offline.

Solution 3:^[3]

I had the same issue and the problem was with the URL, it was https://localhost:8000; in place of http://localhost:8000.

So try checking your URL and routes.

Solution 4:^[4]

My server was just not running locally. :) Starting localhost solved it.

Solution 5:^[5]

Instead of launching your application using the option "Launch Chrome against localhost", rather set your application name for launching - Resolved.

See the attached image for more context.

Enter image description here

Solution 6:^[6]

In my case, it got resolved by closing the browser and recompiling the app.

Solution 7:^[7]

Console error message

I had this same error and I resolved it by turning off my plugins. Specifically a CORS plugin I have been using.

Solution 8:^[8]

Try this:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "request": "launch",
            "name": "Launch Chrome against localhost",
            "type": "dart"
        }
    ]
}

Solution 9:^[9]

For me, the issue was react/next.js application was not running. Basically, you have to keep the application running in a separate window/terminal to be able to attach the debugger. This is unlike the other application where it starts from debug console itself.

Solution 10:^[10]

I have seen a lot of solutions for this problem, but nothing worked.

After a little debugging and commenting out many parts of the code, I managed to locate the issue.

Basically, it occurs on the backend; not the frontend.

There was an infinite loop that kept responses stuck. Fixing that issue, solved it for me.

Solution 11:^[11]

I displaied a similar message in my debug console and the problem was that the local web server was turned off, therefore unreachable. I turned on the server in the virtual machine and the app started working again :-)

Solution 12:^[12]

I ran into this error on 3 separate Next.js projects. Same error in Chrome, Chrome Incognito, Firefox, and Edge. Happened on production build (next build && next start) and dev server (next dev). After trying a number of fixes – ensuring I was on HTTP not HTTPS, checking if port was in use, deleting node_modules and running npm install, etc. – the thing that finally worked was restarting my computer...

Posting here in case anyone has run into this issue when using Next.js – hopefully this helps, and I'd love to hear what causes the error!

Solution 13:^[13]

I had the same issue with an app that needed to run navigator.geolocation.getCurrentPosition in my React application which of course needs HTTPS.

// .env.local HTTPS is set to true
HTTPS=true

The problem - I was loading the page with HTTP and not HTTPS.

Error Screenshot

Solution 14:^[14]

I was able to get mine running by clicking "Add Configuration" and including the command that we specify in our package.json file and use for running during development.

Solution 15:^[15]

This issue I face while debugging in vs code for an Angular application.The probable causes may be the server is not up and listening to port.You may start the server manually by ng serve --port with port number .Also compare URL in lauch.json and compare the port number

Solution 16:^[16]

In my case, I had a Blazor solution and began receiving the Crbug/1173575, non-JS module files deprecated message, besides this, I also received a 404 error for the Index.html file!

The cause was that I inadvertently removed the reference on the .Server project to the .Client project. The project compiled fine without the reference, but I guess Asp.netCore does some sort of reflection-based analysis on the dependencies to dynamically build the route map.

Restoring the reference to the .Client project on the .Server project fixed the problem.

Solution 17:^[17]

In my case it was caused by uBlock origin. Disabling it on the website promptly fixed the error.

I haven't seen anyone mention this yet, so adding my answer.

Solution 18:^[18]

I had a similar issue. However, I discovered a different solution. It's still worth checking the steps in the GitHub link from the OP’s solution.

The project I was working on was made in an older version, and the launch.json URL had // delimiters. Replacing these with no delimiters resolved the issue.

from

"url":"file:///C://exampleParent//exampleChild//file.txt"

 "url":"file:///c:/exampleParent/exampleChild/file.txt"

Solution 19:^[19]

When I try and follow the steps described on Chrome Debugging with Angular CLI, I get a message that the library is no longer supported and a link to this article:

Request’s Past, Present and Future #3142

Solution 20:^[20]

I had encountered the same problem in Visual Studio Code when I tried to debug a Python file. I resolved it by deleting the previous launch.json file and create a new one for this file.

Solution 21:^[21]

I had a similar encounter in a JavaScript project. But I hadn’t learned JSON, but I just deleted the last three commands in the JSON file that is removed the names "url" and "webroot".

Solution 22:^[22]

Checking point (if you are working with a folder/file)

Check the folder/file name
Remove special characters (the folder/file name does not allow special characters)
Debug you code carefully (Java catch exception can't catch those errors)

Solution 23:^[23]

I think we should just remove the cookies in that URL:

Solution 24:^[24]

Open file launch.json and change the port number in “URL” in “configurations” to the port number of the live server.

Solution 25:^[25]

In my case, the problem was because port 4200 was taken by another application (Docker). As soon as I changed the port to 4201 by adding the next structure in the serve section of angular.json file the problem was solved.

"options": {
    "port": 4201
}

Solution 26:^[26]

This may be of use to someone working on a project that communicates across iframes, I found this warning within a current web application: Crbug/1173575, non-JS module files deprecated.

In my case, the reason was that the resource iframe origin wasn't being served meaning the Iframe request URL was not accessible. When serving the resource the warning disappeared.

Solution 27:^[27]

Removing these lines two worked for me. Its an Https error

   var cors = require('cors');
   app.use(cors());

Solution 28:^[28]

To add another angle to this. I named my javascript modules with .mjs after setting my web server to serve mjs with mime type application/javascript I got the error

'crbug/1173575, non-JS module files deprecated.'

None of the answers here helped. To fix it I gave a path to the module.

From

<script type="module" src="xxx.mjs"></script>

<script type="module" src="./xxx.mjs"></script>

And the error went away.

Solution 29:^[29]

In Visual Studio Code you can use the "normal" Dart&Flutter run and debug config. If you don't have an emulator opened, the app will automatically open in the Chrome browser.

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "app",
            "request": "launch",
            "type": "dart"
        },
        {
            "name": "app (profile mode)",
            "request": "launch",
            "type": "dart",
            "flutterMode": "profile"
        }
    ]
}

Tested in VSCode 1.62.3 with Dart 2.14.4 and Flutter 2.8.0-3.3.pre

Solution 30:^[30]

My problem was in the network settings of my Windows 10 computer not on the browser. I have tried my URL in another computer and mobile browsers and it was working fine.

So, I have fixed the issue by resetting my network settings

To do that, go to Settings -> Network and Internet -> Scroll down to network reset

Wait for 5 minute until it restarts.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1	TankorSmash
Solution 2	s0rana
Solution 3	Peter Mortensen
Solution 4	Leon
Solution 5	Peter Mortensen
Solution 6	vsg
Solution 7	Peter Mortensen
Solution 8	Josef
Solution 9	Rahul
Solution 10	Dharman
Solution 11	Pietro La Grotta
Solution 12	Peter Millspaugh
Solution 13	Peter Mortensen
Solution 14	Leif Flor
Solution 15
Solution 16	BlueStrat
Solution 17	supersan
Solution 18	Peter Mortensen
Solution 19	Peter Mortensen
Solution 20	Peter Mortensen
Solution 21	Peter Mortensen
Solution 22	Peter Mortensen
Solution 23	Peter Mortensen
Solution 24	Peter Mortensen
Solution 25	Sergey Stativa
Solution 26	Nick Taras
Solution 27	Kipruto
Solution 28	Jerinaw
Solution 29	creep3007
Solution 30	Abdu

'Crbug/1173575, non-JS module files deprecated. chromewebdata/(index)꞉5305:9:5551

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]

Solution 7:[7]

Solution 8:[8]

Solution 9:[9]

Solution 10:[10]

Solution 11:[11]

Solution 12:[12]

Solution 13:[13]

Solution 14:[14]

Solution 15:[15]

Solution 16:[16]

Solution 17:[17]

Solution 18:[18]

Solution 19:[19]

Solution 20:[20]

Solution 21:[21]

Solution 22:[22]