requests for .map throws 404 if the original library is in a grouped request

[jsdelivr]

requests for .map throws 404 if the original library is in a grouped request

[ryanpitts]

FWIW, specifically adding the .map file to the request:

[email protected](underscore-min.js+underscore-min.map)

Does not help, because dev tools still makes the automatic request to the /g/ directory.

[jimaek]

Not sure how to fix this. I can detect when /g/ gets requested a map file but not I don't know how to figure out what project contains the map file. Not even speaking of the version of the project.

Would it work if I simply responded with an empty 200 reply?

[ryanpitts]

An empty 200 would end up breaking the .map functionality in dev tools too, so that wouldn't be any better than the 404.

The only way I can think to determine which project+version will need the .map file is when you're compiling the minned javascript in the first place. In order to support .map, I believe a js file is supposed to have a line like //# sourceMappingURL=underscore-min.map, so it might be possible to detect that, and as you are minning the file, rewrite the = location to the proper place (which would be whichever directory you're retrieving the actual .min js from).

[jimaek]

The browser makes a separate HTTP request for the map file. So I don't know what URL originally generated the .map request. And I don't want to modify the files in any way. Users should know what they are getting before hand. No on-the-fly rewrites.

I say empty 200 because at least this way there are no warnings/errors. And there is absolutely no reason to use map files in a grouped URL, they are meant for debugging. If you want to debug a library you should do it at least by loading the normal file or even better the unminified one :)

What do you think?

[jimaek]

I deployed the fix. In any case its better to get rid off 404 errors.
Let me know what you think on this topic.

P.S. This is the API repo, you should use jsdelivr/jsdelivr next time for this kind of issues :)

[ryanpitts]

Oh wow, I didn't realize I was leaving issues in the API repo!

You're right, if someone wants to debug a library, they ought to be loading the file independently. Makes sense to me. I wasn't needing to debug, we just noticed the 404.

[brgrz]

Still an issue with this
jsdelivr/jsdelivr#3814