https://www.w3.org/Tools/respec/respec-w3c-common.js.map
Currently this throws HTTP 300 and breaks source mapping. Maybe the server should be configured to correctly redirect it.
Ah, I think the w3c server is specifically configured to only work with the old file name. We might need to switch back to the crappy name.
Or we can get a symbolic link to the new name for compatibility 馃榾 (The builder should not erase the whole directory before build then)
Ok, let's try for that.
@deniak or @tripu, we previously were getting the W3C to serve:
respec/respec-w3c-common.build.js.map
But we renamed that to:
respec/respec-w3c-common.js.map
Would it be possible to get that updated on the w3c side?
Maybe we can also use third-party unpkg.com or rawgit.com, etc...
No, unfortunately. There are a number of privacy concerns around third-parties seeing who is loading which specs (could reveal who is implementing a spec to a third party, for instance)... see also what happened at https://rawgit.com (they are shutting down). The community is are currently dealing with fallout from that too :(
Done. The file should be refreshed automatically, like the rest.
Most helpful comment
No, unfortunately. There are a number of privacy concerns around third-parties seeing who is loading which specs (could reveal who is implementing a spec to a third party, for instance)... see also what happened at https://rawgit.com (they are shutting down). The community is are currently dealing with fallout from that too :(