Javascript Source File Unreadable When Looking On Chrome Stack Overflow

By themelower On Jul 19, 2025

Javascript Source File Unreadable When Looking On Chrome Stack Overflow I'm current new to a project and i've realized that the javascript files that get edited in an ide aren't readable in chrome. for example. the following is a code snippet that i have in intellij. this is in a file called mnv.js, however opening up the mnv.js file on chrome devtools shows this. Keep your client side code readable and debuggable even after you've combined, minified or compiled it. use source maps to map your source code to your compiled code in the sources panel. source maps from preprocessors cause devtools to load your original files in addition to your minified ones.

Javascript Source File Unreadable When Looking On Chrome Stack Overflow Everything works well, except for one important thing: the sources tab in google chrome shows files that are changed so much that they do not look like my code and are unreadable. for example, here is a screenshot of my code:. Useragent: mozilla 5.0 (macintosh; intel mac os x 10 15 7) applewebkit 537.36 (khtml, like gecko) chrome 90.0.4430.93 safari 537.36 steps to reproduce the problem: 1. go to distinct warp air.glitch.me 2. wait until it says 'service worker status: activated' 3. click the 'load broken.js' button. what is the expected behavior? the sources panel shows the loaded file from the source map. This is my first time not using create react app and instead configuring my own webpack files. everything works well, except for one important thing: the sources tab in google chrome shows files that are changed so much that they do not look like my code and are unreadable. I tried to run a file with a .js file included in it but when i ran it with live server extension, i can't see the .js file in the page tab in sources and i can't execute the .js file too.

Javascript Source File Unreadable When Looking On Chrome Stack Overflow This is my first time not using create react app and instead configuring my own webpack files. everything works well, except for one important thing: the sources tab in google chrome shows files that are changed so much that they do not look like my code and are unreadable. I tried to run a file with a .js file included in it but when i ran it with live server extension, i can't see the .js file in the page tab in sources and i can't execute the .js file too. When i checked it, all javascript file is loading in unreadable format. see image below. i tried to replace that character with its unicode " " and saved all js files in default encoding, but didn't help. do anyone know why is this happening?. In jquery's defense, the source is multiple files on which the build script is executed: github jquery jquery tree master src . (unfortunately, still unreadable in its structure, organization, quality, etc.). I have a script that loads fine in chrome, but not firefox or ie. i get an error console messages loading failed for the