[Solved] jQuery’s jquery-1.10.2.min.map is triggering a 404 (Not Found)
I’m seeing error messages about a file,
min.map, being not found:
GET jQuery’s jquery-1.10.2.min.map is triggering a 404 (Not Found)
Where is this coming from?
If Chrome DevTools is reporting a 404 for a .map file (maybe
jquery-2.0.3.min.map, but can happen with anything) first thing to know is this is only requested when using the DevTools.
Your users will not be hitting this 404.
Now you can fix this or disable the sourcemap functionality.
Fix: get the files
Next, it’s an easy fix. Head to http://jquery.com/download/ and click the Download the map file link for your version, and you’ll want the uncompressed file downloaded as well.
Having the map file in place allows you do debug your minified jQuery via the original sources, which will save a lot of time and frustration if you don’t like dealing with variable names like
Dodge: disable sourcemaps
Use the cog icon in the bottom right of the DevTools, to open settings, then:
You can remove the 404 by removing the line
from the top part of your jQuery file.
The top part of the jQuery file will look like this.
/*! jQuery v1.10.2 | (c) 2005, 2013 jQuery Foundation, Inc. | jquery.org/license //@ sourceMappingURL=jquery-1.10.2.min.map */
Just change that to
/*! jQuery v1.10.2 | (c) 2005, 2013 jQuery Foundation, Inc. | jquery.org/license */
Purpose of a source map
(Read more on this here)
As it is announced in
jQuery 1.11.0/2.1.0 Beta 2 Released the source map comment will be removed so the issue will not appear in newer versions of
Here is the official announcement:
One of the changes weâ€™ve made in this beta is to remove the sourcemap
comment. Sourcemaps have proven to be a very problematic and puzzling
thing to developers, generating scores of confused questions on forums
like StackOverflow and causing users to think jQuery itself was
Anyway, if you need to use a source map, it still be available:
Weâ€™ll still be generating and distributing sourcemaps, but you will
need to add the appropriate sourcemap comment at the end of the
minified file if the browser does not support manually associating map
files (currently, none do). If you generate your own jQuery file using
the custom build process, the sourcemap comment will be present in the
minified file and the map is generated; you can either leave it in and
use sourcemaps or edit it out and ignore the map file entirely.
Here you can find more details about the changes.
Here you can find confirmation that with the
jQuery 1.11.0/2.1.0 Released the source-map comment in the minified file is removed.
The new versions of jQuery require this file http://code.jquery.com/jquery-1.10.2.min.map
The usability of this file is described here http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/
// sourceMappingURL comment is not included in the compressed file.
If you want to get source map file different version, you can use this link
Instead x.xx.x put your version number.
Note: Some links, which you get on this method, may be broken 🙂
As I understand the browser, Chrome at least, it doesn’t disable the source mapping by default. That means your application’s users will trigger this source-mapping request by default.
You can remove the source mapping by deleting the
After following the instructions in the other answers, I needed to strip the version from the map file for this to work for me.
I was using a
; as a separator which caused the path to the source map to 404.
So dev tools was looking for
jquery.min.map; instead of
I know that isn’t the answer to the original question, but I am sure there are others out there with a similar Grunt configuration.
jQuery 1.11.0/2.1.0 the // sourceMappingURL comment is not included in the compressed file.
Assuming you’ve checked the file is actually present on the server, this could also be caused by your web server restricting which file types are served: