Description
What is the problem this feature will solve?
It seems it isn't possible to load external sourcemaps in Node.
Let's say our sourcemap URL is https://example.com/foo.js.map
, Chrome will fetch this in the context of the page you're on afact. This means it will successfully load as long as CORS is satisfied and what not.
However, if we try the same with node, we get this non-helpful error (which could also do with improvement):
DevTools failed to load source map: Could not load content for https://example.com/foo.js.map: Fetch through target failed: 'Network.loadNetworkResource' wasn't found; Fallback: Unknown error
Presumably this means we need to implement support for the following in Node:
https://chromedevtools.github.io/devtools-protocol/tot/Network/#method-loadNetworkResource
is this possible these days? this affects debugging a lot since even some locally hosted URLs run into this problem (e.g. if your sourcemap URL is http://localhost:1234/foo.js.map
or something).
What is the feature you are proposing to solve the problem?
Implement loadNetworkResource
(and probably the rest of the Network
namespace)
What alternatives have you considered?
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status