12

I am working on a node.js API. We use typescript and I use Chrome dev tools for debuging. In the last day when I started the chrome node inspector it could not load my resource maps. I tried making a small mock project and it happened for that one too.

The warning it gives is DevTools failed to load source map: Could not load content for file://<path_to_source_map>: No setting registered: network.enable-unc-loading. I have the latest version of chrome 105 and I am on macOS 12.5.1.

I was thinking it might have something with mac permission but when I take the link to the file file://<path_to_source_map> and open it in browser it can open my file and I can add the file trough workspaces but it cannot link them even if I do it manually. I do not know if it is a chrome setting or what.

Any ideas ?

3
  • 3
    This is very weird. This issue also appeared for me just this morning, but I use inline source maps encoded as base64. Pasting the base64 code into the search browser search bar correctly decodes it. This seems to be an issue with the 105 release of Chrome as I tested 104 and everything works. I opened an issue here: bugs.chromium.org/p/chromium/issues/detail?id=1360298 Commented Sep 6, 2022 at 6:23
  • When I click file://<path_to_source_map> it is opened as about:blank on the chrome by the way Commented Sep 7, 2022 at 13:57
  • Anyone know the cause? I'm getting these errors in windows, node, chrome 105.0.5195.102 (Official Build) (64-bit)? Im getting same thing on my mac. My co-worker on the otherhand (mac w/ same versions) is not. Commented Sep 12, 2022 at 17:40

1 Answer 1

2

I've found this setting:

network.enable-unc-loading

But this setting is not available in the Dev Tools console for Remote Targets so it didn't fix the issue.

Sign up to request clarification or add additional context in comments.

5 Comments

This setting is present for me in Node.js DevTools in Canary 107.0.5290.1.
And while it didn't work at first, eventually that made it work for me.
also don't have this setting. Been debugging until today and now it seems everyone has the same issue.
In my case, I have updated chrome and now it works again.
This issue started happening for me in Brave Version 1.44.105 Chromium: 106.0.5249.91 (Official Build) (64-bit) I switched to Chrome Version 106.0.5249.91 (Official Build) (64-bit) and the issues does not occur. 🤷‍♂️

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.