357

I'm trying to display an image selected from the local machine and I need the location of that image for a JavaScript function. But I'm unable to get the location.

To get the image location, I tried using console.log, but nothing returns.

console.log(document.getElementById("uploadPreview"));

Here's the HTML code:

<!DOCTYPE html>
<html>
<head>
  <title></title>
</head>

<body>
  <div align="center" style="padding-top: 50px">
    <img align="center" id="uploadPreview" style="width: 100px; height: 100px;" />
  </div>

  <div align="center" style="padding-left: 30px">
    <input id="uploadImage" type="file" name="myPhoto" onchange="PreviewImage();" />
  </div>

  <script type="text/javascript">
    function PreviewImage() {
      var oFReader = new FileReader();
      oFReader.readAsDataURL(document.getElementById("uploadImage").files[0]);

      oFReader.onload = function (oFREvent) {
        document.getElementById("uploadPreview").src = oFREvent.target.result;
        console.log(document.getElementById("uploadPreview").src);

      };
    }
  </script>

</body>
</html>

Console Output:

Enter image description here

Here's the warning:

DevTools failed to load SourceMap: Could not load content for chrome-extension://alplpnakfeabeiebipdmaenpmbgknjce/include.preload.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

xDan
  • 19
  • 3
snehit vaddi
  • 3,854
  • 2
  • 9
  • 13
  • 39
    If you click the link you'll see in the url that it's related to an extension. Probably AdBlock. – Juan Carlos Puerto May 26 '20 at 22:00
  • 3
    @JuanCarlosPuerto I had 10 of these warnings on my Drupal website. Disabled AdBlock and Brave Shields, now I only have 2. Thanks! – Chris Rahmé Aug 28 '20 at 21:46
  • 1
    Possibly relevant: [DevTools failed to load SourceMap: Could not load content](https://stackoverflow.com/questions/61205390/why-when-adding-a-javascript-library-browsers-complain-about-a-missing-source) (Thought it's a slightly different error: "HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE") – Scratte Feb 05 '21 at 00:13
  • 2
    In my case help me deactivate Loom for Chrome. I test deactivating other extensions but the only one with the problem was Loom. – Erick Mar 17 '21 at 16:40
  • Similar (posted the day before): *[When adding a JavaScript library, Chrome complains about a missing source map. Why?](https://stackoverflow.com/questions/61205390/)*. Probably the same root cause (support was added for source maps in Chrome). – Peter Mortensen Sep 10 '21 at 17:58
  • I found this line of code in my case. For the error to be fixed, I removed this line. /*# sourceMappingURL=tailwind.css.map */ – Jasp402 Oct 29 '22 at 17:27

21 Answers21

467

That's because Chrome added support for source maps.

Go to the developer tools (F12 in the browser), then select the three dots in the upper right corner, and go to Settings.

Then, look for Sources, and disable the options:

  • "Enable JavaScript source maps"
  • "Enable CSS source maps"

If you do that, that would get rid of the warnings. It has nothing to do with your code. Check the developer tools in other pages and you will see the same warning.

Diego Oña
  • 5,091
  • 1
  • 7
  • 7
  • 141
    I have faced the same issue. Your answer gets rid of the warning, but do you know the proper solution instead of just disabling it? I mean why the warning is triggering to begin with? I am new to these source maps stuff. – iVoidWarranties May 17 '20 at 16:19
  • 125
    Everyone, please note that this answer DISABLES source maps in the dev tools. Make sure that's what you want. – Jack Steam Jun 08 '20 at 20:10
  • 7
    This works great but it has a side effect. It changes the file name and line that a console log comes from. If you put a log in a js file it indicates the compiled es5 file (main.chunk.js: line number) instead of the actual file (f.i index.js: line) – kboul Jun 12 '20 at 14:24
  • 2
    For me this worked since it stopped the warnings but did not disable the sourcemap from webpack – franksands Jul 08 '20 at 12:24
  • 6
    mine was caused by a webpack-config. I changed the config to include `devtool: 'inline-source-map',` as [aiibe mentioned on github](https://github.com/webpack/webpack-dev-server/issues/1161#issuecomment-345940858). Just mentioning it here in case somebody comes across the same issue and finds this first ;) – MMachinegun Oct 07 '20 at 21:43
  • That's works. other pages also showing this warning. But when I disable "Enable JavaScript source maps" its fix the issue. I think this issue only for the Chrome, I tried with Opera GX and it's worked fine. – Nuwan Dissanayaka Oct 08 '20 at 04:02
  • 3
    @MMachinegun, I have many instances of the webpack-config in my application's ecosystem. How did you know which to change? I get this error for `injectGlobalHook.js.map`, `react_devtools_backend.js.map`, and `contentScript.js.map` – Jay J Oct 25 '20 at 18:30
  • 1
    @JayJ not sure which project I came across this issue, but most of the time I only have one config file for webpack, which is sat in the root of the project. So maybe some trial and error, add it in all of them (if they're not too many) and see if it resolves it. If yes, remove one after the other to see which ones actually need that setting to resolve those errors. Just my first thoughts of what I might try to do. – MMachinegun Oct 25 '20 at 20:08
  • 2
    facing the same issue for injectGlobalHook.js.map, react_devtools_backend.js.map, and contentScript.js.map files. – Or Assayag Oct 26 '20 at 09:18
  • While this was helpful, it prevents your own source code from being mapped so it can be debugged. The better solution is to determine which extensions are causing the issues and then handle those extensions as explained in my answer below. – Danny Remington - OMS Mar 10 '21 at 17:24
  • yes see github [here] if this hapen using vscode (https://github.com/Microsoft/vscode/issues/34385#issuecomment-777191202) – user1767316 Apr 23 '21 at 05:15
  • 3
    Disabling the feature that shows a warning message has never been a real solution for the original issue in the warning message. Ever. – Tim Jun 11 '21 at 03:31
  • @Tim Fua, la re vivís escubi – Diego Oña Jun 12 '21 at 15:00
  • 2
    it is only hiding the warning, its not correct – Asfandyar Khan Aug 25 '21 at 14:07
  • 1
    This is not a good solution for most developers. I don't think I am speaking for just myself when I say that this feature of Chrome is very important. The Javascript source maps are useful to those who need to debug their minified/transpiled code... – austinw Jan 01 '22 at 06:19
  • It's not good solution, the good solution is here: https://stackoverflow.com/a/67559032/1407491 – Nabi K.A.Z. Feb 20 '22 at 16:51
  • Why would it give a warning though? I mean, it's like Chrome adding a warning for "you did not add some tag that we think you should have in your HTML"... like, that's super-arbitrary. Why does Google think a source map is in some way necessary for a web page to run properly? – SteveExdia May 04 '22 at 18:48
  • Thank you! This helped me with error logs I was getting with graphql/graphiql https://github.com/graphql/graphiql – Anthony Peña Jul 25 '22 at 15:43
  • I need the source maps, so "Selected context only" works perfect for me. – Guntram Dec 05 '22 at 13:23
  • The warning message specifies an issue with an Extension, so start there. Rather than turning of the source maps feature (as pointed out in other comments here), try disabling Extensions one-by-one, as proposed in the answer by Danny Remington - OMS, which addresses the warning message directly, provides examples, and step-by-step which aren't difficult and can be undone easily. – Jonru Dec 30 '22 at 17:57
  • I had to disable the True Key extension which was causing this source map errors, disabling this setting in Chrome Inspect is a wrong approach to solve this issue. – Arunkumar Arjunan Jan 01 '23 at 00:31
  • I have those two checkboxes already ticked, but I still have two of these warnings. Why? – Andrew Truckle Feb 21 '23 at 18:35
  • To me, this answer is similar to saying 'if you just turn off your computer, you wont see the error messages anymore' – 22289d Jul 25 '23 at 11:52
157

Go to Developer tools → Settings → Console → tick "Selected context only". The warnings will be hidden. You can see them again by unticking the same box.

The "Selected context only" means only the top, iframe, worker and extension contexts. Which is all that you'll need, the vast majority of the time.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Chandima
  • 2,061
  • 1
  • 13
  • 6
115

Fixing "SourceMap" error messages in the Development Tools Console caused by Chrome extensions:

Examples caused by McAfee extensions:

DevTools failed to load SourceMap: Could not load content for chrome-extension://klekeajafkkpokaofllcadenjdckhinm/sourceMap/content.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

DevTools failed to load SourceMap: Could not load content for chrome-extension://fheoggkfdfchfphceeifdbepaooicaho/sourceMap/chrome/content.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

DevTools failed to load SourceMap: Could not load content for chrome-extension://fheoggkfdfchfphceeifdbepaooicaho/sourceMap/chrome/iframe_handler.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

If you are developing, then you need "Enable JavaScript source maps" and "Enable CSS source maps" checked to be able see your source code in Chrome Developer Tools. Unchecking those takes away your ability to debug your source code. It is like turning off the fire alarm instead of putting out the fire. You do not want to do that.

Instead you want to find the extensions that are causing the messages and turn them off. Here is how you do that:

  1. Go to the three dots in the upper right hand corner of Chrome.
  2. Go to "More Tools" and click on "Extensions".
  3. Do this for one extension at a time until no more "SourceMap" errors are in the console:
    1. Turn off the extension by sliding the switch to the left.
    2. Reload the page that you were using the Development Tools on.
    3. Check if any of the "SourceMap" error messages disappeared.
      1. If any did, then that extension was causing those messages.
      2. Otherwise, that extension can be turned back on.

After determining which extensions caused the issue either:

  1. If you need it, then contact the maker to have them fix the issue.
  2. Otherwise, remove the extension.
Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Danny Remington - OMS
  • 5,244
  • 4
  • 32
  • 21
  • 2
    This did the trick. I did not need to "Do this for one extension at a time" because the extension code shown in the extension list matched part of the error string. Thank you for providing the solution that "fixes" the issue instead of turning off or disabling Chrome features. – Neil_Tinkerer Mar 31 '21 at 17:57
  • 1
    In my case it was "Selenium IDE" extension – Alex Buchatski Jul 08 '21 at 15:16
  • and in my case Keeper extension – user0810 Sep 29 '21 at 18:12
  • 6
    Agree with @Danny Remington - OMS. The answer with the most upvotes is not the best. As Danny put it: "It is like turning off the fire alarm instead of putting out the fire." You need to fix the underlying issue. – Robin Zimmermann Apr 20 '22 at 19:24
  • 19
    For me, its was Adblock that caused error message – nuicca Jul 10 '22 at 12:30
  • 5
    +1 This is the best answer. For me, it was AdBlock that caused the error as well. It didn't help to disable it for the current page, I had to disable the extension. – happybits Oct 04 '22 at 12:38
  • What if there is no 'Extensions' option under 'More tools'? Perhaps they moved it recently or something is off on my config? – Dylan Glockler Dec 16 '22 at 14:45
  • 3
    You can also just google the extension ID in the URL to find the offender. For example, googling `klekeajafkkpokaofllcadenjdckhinm` has [McAfee](https://chrome.google.com/webstore/detail/mcafee%C2%AE-web-boost/klekeajafkkpokaofllcadenjdckhinm?hl=en) as the first result. – asportnoy Feb 14 '23 at 05:20
  • I have turned of all my extensions and the error is still there. My specific message says: `DevTools failed to load source map: Could not load content for file:///Users/yoyoyojoe/Documents/file_path/examine_the_page/bootstrap.min.css.map: System error: net::ERR_FILE_NOT_FOUND` & `DevTools failed to load source map: Could not load content for file:///Users/yoyoyojoe/Documents/file_path/examine_the_page/bootstrap.bundle.min.js.map: System error: net::ERR_FILE_NOT_FOUND`, while the `index.html` does not refer to those files. Any other clues? – yoyoyojoe Mar 01 '23 at 00:19
  • This is really right answer!!!!! Fix my problem!!!Thank you very much ! Have a Nice day!!! – Kevin Aug 11 '23 at 14:14
  • this helped! For me it was ChroPath extension for selectors – FlavioR Aug 11 '23 at 23:52
57

I stumbled upon this Stack Overflow question after discovering loads of source map errors in the console for the Edge browser. (I think I had disabled the warnings in the Chrome browser long ago.)

For me it meant first realising what a source map is; please refer to Macro Mazzon's answer to understand this. Since it's a good idea, it was just a case of finding out how to turn them on.

It's as simple as adding this line in your webpack.config.js file -

module.exports = {
    devtool: "source-map",
}

Now that Edge could detect a source map, the errors disappeared.

user1849962
  • 1,273
  • 1
  • 11
  • 16
54

The include.prepload.js file will have a line like below, probably as the last line:

//# sourceMappingURL=include.prepload.js.map

Delete it and the error will go away.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Ravikiran kalal
  • 1,050
  • 8
  • 11
  • This solution works for me too. But the line was inside js.cookie.min.js – Rubyx Sep 11 '20 at 15:59
  • 1
    Yeah I just solved my problem (with the React Developer Tools extension) in this same way. I had to find the three React DevTools files that were being complained about, delete the sourcemapping comments out of them, and restart Chrome. Then things were fine. Hooray for hacks! – mjwach Nov 03 '20 at 17:22
  • 6
    This is the proper solution instead of working around by disabling maps or ignoring warnings. – Khalid Abu Shawarib Jun 10 '21 at 12:48
  • 1
    That line has apparently been [inserted by a minification tool](https://stackoverflow.com/questions/21719562/how-can-i-use-javascript-source-maps-map-files/36554691#36554691). – Peter Mortensen Sep 11 '21 at 14:42
33

For me, the problem was caused not by the application in development itself, but by the Chrome extension React Developer Tool. I solved it partially by right-clicking the extension icon in the toolbar, clicking "Manage extension" and then enabling "Allow access to files URLs." But this measure fixed just some of the alerts.

I found issues in the React repository that suggests the cause is a bug in their extension and is planned to be corrected soon - see issues 20091 and 20075.

You can confirm is extension-related by accessing your application in an anonymous tab without any extension enabled.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
João Melo
  • 784
  • 6
  • 16
21

Chrome has changed the UI in 2022, so this is a new version of the most upvoted reply.

  1. Open the dev tools (hit F12 or Option + Command + J)
  2. Select the gear at the top. There are two gears in that area, so be sure to select the one at the top, top.
  3. Locate the Sources section
  4. Deselect "Enable JavaScript source maps"

Check to see if it worked!

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Nichlas tm
  • 329
  • 2
  • 5
16

Right: it has nothing to do with your code. I've found two valid solutions to this warning (not just disabling it). To better understand what a source map is, I suggest you check out this answer, where it explains how it's something that helps you debug:

The .map files are for JavaScript and CSS (and now TypeScript too) files that have been minified. They are called SourceMaps. When you minify a file, like the angular.js file, it takes thousands of lines of pretty code and turns it into only a few lines of ugly code. Hopefully, when you are shipping your code to production, you are using the minified code instead of the full, unminified version. When your app is in production, and has an error, the sourcemap will help take your ugly file, and will allow you to see the original version of the code. If you didn't have the sourcemap, then any error would seem cryptic at best.

  1. First solution: apparently, Mr Heelis was the closest one: you should add the .map file and there are some tools that help you with this problem (Grunt, Gulp and Google closure for example, quoting the answer). Otherwise you can download the .map file from official sites like Bootstrap, jQuery, font-awesome, preload and so on... (maybe installing things like popper or swiper by the npm command in a random folder and copying just the .map file in your JavaScript/CSS destination folder)

  2. Second solution (the one I used): add the source files using a CDN (content delivery network). (Here are all the advantages of using a CDN). Using content delivery network (CDN) you can simply add the CDN link, instead of the path to your folder. You can find CNDs on official websites (Bootstrap, jquery, popper, etc.) or you can easily search on some websites like Cloudflare, cdnjs, etc.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Marco Mazzon
  • 327
  • 4
  • 15
  • 1
    Actually the most useful answer – Gonzalo F S Mar 30 '23 at 10:47
  • There's zero point in downloading source maps for Bootstrap/jQuery/etc. If you wanted to debug this stuff you wouldn't use the minified sources anyway. Much simpler just to ignore these non-warnings. – EML Aug 29 '23 at 09:18
11

Extensions without enough permissions on Chrome can cause these warnings, for example for React developer tools. Check if the following procedure solves your problem:

  1. Right click on the extension icon.

Or

  1. Go to extensions.
  2. Click the three-dot in the row of React developer tool.

Then choose "This can read and write site data".

You should see three options in the list. Pick one that is strict enough based on how much you trust the extension and also satisfies the extension's needs.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Mooventhan
  • 121
  • 1
  • 4
  • Removing React developer tools removed the warning for me. It was showing up on all non React sites. – Ronni DC Nov 01 '20 at 22:32
  • @RonniDC It is enough if you follow these answer steps and select the first option _When you click the extension_. Not necessary to uninstall the extension. – Guillermo Garcia Nov 07 '20 at 01:04
6

I appreciate this is part of your extensions, but I see this message in all sorts of places these days, and I hate it: how I fixed it (this fix seems to massively speed up the browser too) was by adding a dead file

  1. physically create the file it wants it/where it wants it, as a blank file (for example, "popper.min.js.map")

  2. put this in the blank file

    {
 "version": 1,
 "mappings": "",
 "sources": [],
 "names": [],
 "file": "popper.min.js"
}

  3. make sure that "file": "*******" in the content of the blank file matches the name of your file ******.map (minus the word ".map")

(I suspect you could physically add this dead file method to the addon yourself.)

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Mr Heelis
  • 2,370
  • 4
  • 24
  • 34
  • 5
    My browser lists the desired files are chrome extensions for example: `chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/injectGlobalHook.js.map`. Where would that location be in the file system? – Jay J Oct 25 '20 at 08:08
  • 1
    @JayJ See here: https://stackoverflow.com/questions/14543896/where-does-chrome-store-extensions – krm Apr 24 '23 at 21:00
  • @MrHeelis: Unfortunately, after I applied your solution to an extension, then Chrome has disabled that extension, showing a message "This extension may be corrupted". It was only possible to click "Repair this extension" to enable it again. The repair process has removed the dead file which I had added, because it has reinstalled the extension. – krm Apr 24 '23 at 21:06
5

I do not think the warnings you have received are related. I had the same warnings which turned out to be the Chrome extension React Dev Tools. I removed the extension and the errors were gone.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Jozadad1
  • 79
  • 1
  • 2
3

You have just missing files.

Go to the website https://www.cdnpkg.com/. Download what you need and copy it to the right folder.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Panda
  • 79
  • 2
3

For me, the warnings were caused by the Selenium IDE Chrome extension. These warnings appeared in the Console on every page load:

DevTools failed to load source map: Could not load content for chrome-extension://mooikfkahbdckldjjndioackbalphokd/assets/atoms.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load source map: Could not load content for chrome-extension://mooikfkahbdckldjjndioackbalphokd/assets/polyfills.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load source map: Could not load content for chrome-extension://mooikfkahbdckldjjndioackbalphokd/assets/escape.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load source map: Could not load content for chrome-extension://mooikfkahbdckldjjndioackbalphokd/assets/playback.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load source map: Could not load content for chrome-extension://mooikfkahbdckldjjndioackbalphokd/assets/record.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

Since Selenium IDE was already set to be able to read site data on all sites, I uninstalled it. (I read in another comment here that you might try enabling more permissions for an extension instead of removing it.) In my case, removing Selenium IDE (Chrome extension) got rid of the warnings.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
jdempcy
  • 136
  • 1
  • 4
3

I had the same problem. I tried to disable the extensions one by one to check it, and finally realized I had Adblock enabled, which was causing this issue. To remove that error I followed the step below,

  1. Three dots (top right corner).
  2. Click More tools --> extensions.
  3. Disable the Adblock.
  4. Reload the page.

And it should work now.

Harsh Rathod
  • 129
  • 1
  • 4
3

DevTools failed to load source map: Could not load content for chrome-extension://cfhdojbkjhnklbpkdaibdccddilifddb/browser-polyfill.js.map: System error: net::ERR_FILE_NOT_FOUND

Disable the Chrome extension "Adblock Plus - free ad blocker". https://chrome.google.com/webstore/detail/adblock-plus-free-ad-bloc/cfhdojbkjhnklbpkdaibdccddilifddb

Lately this error is caused by the extension.

Avatar
  • 14,622
  • 9
  • 119
  • 198
  • It works, can someone explain why is it and if there is a chance to use the extension without the error in react – Timo Apr 02 '23 at 10:48
  • 1
    You can use Brave browser which has an adblocker and a track-blocker included. – Avatar Apr 03 '23 at 04:41
2

It is also possible to add the file that is missing, aside with other .js libraries in the same folder (no need to reference the .map in the .html file, <script> tag).

I had the same error, when trying to code in Backbone.js.

The problematic file was backbone-min.js, and the line that created the error was sourceMappingURL=backbone-min.map.

After downloading the missing file (the link comes from here), the error disappeared.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Léa
  • 51
  • 5
1

Problems with Debugging and Sourcemaps in Web Browsers

Hope this clarifies the technicals behind the problem...knowing how things works helps some :)

This browser error means it has some compiled version of your JavaScript in a sourcemap intermediate file it or some 3rd party created that is now needed when debugging that same script in "devtools" in your web browser.

This can happen if your script fails (or in your case trying to get an image source hidden in the sourcemap code that created the script) but whose script error is tied to some JavaScript that got created from an original sourcemap file that now cannot be found to debug that same error. So it's an error about an error, a missing debugging file creating a new error. (crazy, huh?)

This error is likely coming from an extension in the web browser and is reporting it has generated a script error it has recorded in the console.log window of devtools (press F12 in the browser). The error is likely from the extension (not your code) saying it has some code that contains an address to a sourcemap file it cannot access, has a bad URI/URL address, is blocked, or that is missing.

The browser only needs this sourcemap file if a developer using devtools will need to debug the original script again.

A sourcemap, by the way, is a file that translates or transpiles code from one language to another language. Often this is a file that the browser uses to translate this source code into a child script like JavaScript/ECMAScript, or when it needs to do the opposite and recreate the source file from the child script. In most cases this file is not needed at all as a 3rd party software program has already compiled or transpiled the source code into the child script for the browser. For example, developers who like TypeScript use it to create JavaScript. This source code gets transpiled into JavaScript so the browser script engine can run it. The URI/URL to this sourcemap file is usually at the top of the javaScript or application compiled code file in a format like //#....

When this intermediary transpile file is missing or blocked for security reasons in a web browser, the application will usually not care unless it needs the source file for debugging the child script using this source file. In that case it will complain when it feels it needs this file and cannot find it, as it uses it to recreate the source file for the code running in the browser when debugging the script in order to allow a developer to debug the original source code. When it cannot find it, it means that any developer trying to debug it will not be able to do so, and is stuck with the compiled code only. So it is safe to turn off these errors in the various ways mentioned in this post. It should not affect your own scripts if it is connected to an extension. Even if it is related to your own scripts, it is still unlikely you need it unless you plan to run debugging from devtools.

danronmoon
  • 3,814
  • 5
  • 34
  • 56
Stokely
  • 12,444
  • 2
  • 35
  • 23
1

Deactivate the AdBlock extension (the one with a white hand on a red background) and chrome should load all source maps quite well.

But do NOT disable :

  • The options JS sources maps.
  • The options CSS sources maps.
filouDcode
  • 33
  • 5
0

In my case, it was JSON Viewer extension that was blocking the source map files from being loaded

SayJeyHi
  • 1,559
  • 4
  • 19
  • 39
0

In my case i made silly mistake by adding bootstrap.min.js instead of bootstrap.bundel.js :)

Mohammed Yousuff
  • 122
  • 1
  • 1
  • 9
-3

You need to open Chrome in developer mode: select More tools, then Extensions and select Developer mode

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
lamrini
  • 3
  • 1