The following blog post is written to help you answer the VM305:5551 crbug/1173575, non-JS module files deprecated error when trying to run Javascript. Let’s take a deep dive into how this situation came about and how to fix it.
What Causes The VM305:5551 crbug/1173575, non-JS module files deprecated Error?
We were recently receiving the following error. The error is displayed in the browser’s console, and the js file also isn’t processed.
“VM305:5551 crbug/1173575, non-JS module files deprecated.”What Can We Do To Fix It?
The solution for this error is quite simple, you need to find and delete the launch.json module, and the problem is fixed. We started a fresh project and used F5 or Ctrl + F5 to launch it. The following error was presented when we clicked the “Exceptions caught” checkbox.
“at HTMLAnchorElement.eval
(eval at B (chrome-error://chromewebdata/:2:404), <anonymous>:1:41)
at y (chrome-error://chromewebdata/:5552:2740)
at F.b (chrome-error://chromewebdata/:5560:108)
at F.g (chrome-error://chromewebdata/:5558:462)
at window.jstProcess (chrome-error://chromewebdata/:5561:847)
at chrome-error://chromewebdata/:5562:60”.
When not clicking “Exceptions caught”, the next error would be “crbug/1173575, non-JS module files deprecated.”
The following is our launch.json file 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}"
“webRoot”: “${workspaceFolder}"
The Solution
Solution 1
We find and delete the launch.json module, which the problem is resolved at ease.
Solution 2
The following solution is found when we encounter the problem and apply the deleting launch.son file solution to fix it, but it did not work. We tried to open the file and noticed that the URL is http://localhost:8080 rather than its URL.
Our solution was to change http://localhost:8080 to the location of our HTML page, and everything functioned back normally.
Conclusion
The article was the solution for resolving VM305:5551 crbug/1173575, non-JS module files deprecated error. The solution is pretty clear, delete the launch.json file, and the problem is solved.
However, when the main solution failed, we tried to change the URL from localhost to the original HTML site. Hope you find our solutions helpful! Please send your ideas and answers that most suit you for us in the comment section below. Thank you!
Related articles
- Definition about Basic Math Functions.
Java, which is an important programming language, is a popular program computer in the world. Java is also used for: mobile applications (especially Android apps; desktop applications; web applications; web servers and application servers; database connection; and much more. Above the key information of Java, we have the answer for why we use Java. Moreover, […]
- The simple way to fix “Unable to resolve dependency tree” in Reactjs
Each of these pieces of code can depend on a lot of other open source code, fortunately when library management tools came out, otherwise it would take a lot of work to manage these libraries. With npm, the work will be much simpler, they help you make the management much simpler. The libraries are all […]
- Instruction about “Arrays within a Class”.
Before you know about the “Arrays within a Class”, we will help to identify the necessary information of object oriented programming language. It is a useful definition in this program language before you can explore the classes and objects that Arrays within a Class belong to. If you have been waiting for our instruction, we […]
- Tips On Handling The Error “ModuleNotFoundError: No module named ‘tensorflow.python.saved_model.model_utils’”
One of the common problems that developers face when working with Android devices is the error – The emulator process for AVD Pixel_C_API_30 was killed. This problem can usually be solved by changing the AVD configuration or upgrading the device driver. This blog will help you to fix this issue. How To Handle The Error […]
- Tips On Handling The Error “The emulator process for AVD Pixel_C_API_30 was killed” In Windows
One of the common problems that developers face when working with Android devices is the error – The emulator process for AVD Pixel_C_API_30 was killed. This problem can usually be solved by changing the AVD configuration or upgrading the device driver. This blog will help you to fix this issue. How To Handle The Error […]