Denying load of chrome-extension://.../jquery.min.map. Resources must be listed in the web_accessible_resources manifest key in order to be loaded by pages outside the extension.

[tupton]

I get a console error when loading any page with the dotjs extension enabled. Disabling the extension makes the error go away.

Denying load of chrome-extension://dlnccnmhpmdidoiecanghgienhoglnim/jquery.min.map. Resources must be listed in the web_accessible_resources manifest key in order to be loaded by pages outside the extension.

Googling for this error results in this SO question and answer, which mentions including the jquery map.

Is there a known workaround for this?

[tupton]

Did I report this in the correct area? I love almost everything about dotjs, but having these errors in the console is infuriating while debugging or while using jsfiddle. I would love to get an explanation or a pointer to where to start looking to fix it.

[matthewhadley]

The jquery file in dotjs is trying to pull in a source map. This only happens with chrome console open.

Two ways to fix this. You can disable all source maps, details here:
http://stackoverflow.com/a/18365316

Or you can go into dotjs jquery.js and remove the sourcemap comment that enables this:

//@ sourceMappingURL=jquery.min.map

To find the file, open chrome://extensions/ and take note of the id for dotjs

Note the highlighted ID value. Assuming you are using the default user profile, the file is likely at:

~/Library/Application Support/Google/Chrome/Default/Extensions/<ID>/2.0.1_0/jquery.js

After removing the comment, disable then re-enable dotjs.

[tupton]

Thank you so much for the explanation and the pointer to how to fix it! That did it.

[jfexyz]

This is a bug with the dotjs extension. Yes, users can fix it by editing the source, but problem is that either the dotjs extension should include the jquery sourcemap with the extension, or it should remove the sourcemap comment from the jquery file.

Alternatively, dotjs could upgrade jquery; as of 1.11.0 the sourcemap comment is excluded.

[lepht]

@joshuajabbour 👍 This should be resolved in dotjs, imo

[f3ndot]

@joshuajabbour 👍

[tupton]

Let's re-open this so it possibly gets more visibility. There is a workaround, but this does still need to be fixed.

[tupton]

Updating jquery is straightforward: just copy the latest jquery into ext/jquery.js.

You can then load an extension in Chrome by checking the "Developer mode" checkbox at the top of the extensions page and clicking "Load unpacked extension..." Open the ext folder, disable or uninstall the old extension, and now you've got the latest jquery loaded in dotjs.

[Peeja]

It's pretty clear @defunkt isn't maintaining dotjs any longer. Has anyone taken it over yet? (I suppose, if the answer is no, that that's an offer.)

[matthewhadley]

The chrome tabs api has functions to inject js and css, so I made a quick attempt to reproduce dotjs functionality using that: https://github.com/diffsky/chromedotfiles