Fix source map loading for Node.js

Loading source maps requires checking the value of a setting. This
setting was put into the Network module since its related to loading
source maps over the network.

This breaks Node.js debugging since the Node.js DevTools doesn't have
a network panel so the setting gets never registered. This causes all
source map loads to fail.

The solution is to put the setting into `sdk` which is guaranteed to
be loaded everywhere.

R=​kimanh@chromium.org

Fixed: 1358497
Change-Id: I554d2fe7774a620d7cf5b19d3f9bcae5bfd246e5
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3864094
Reviewed-by: Kim-Anh Tran <kimanh@chromium.org>
Commit-Queue: Simon Zünd <szuend@chromium.org>
(cherry picked from commit 789e8b7b52b6a513d5fdd07c3dea7b7687fcccf9)
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3876144
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
4 files changed
tree: a8ffc14678c1cebd3771e96a98cac3b41014e26b
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. front_end/
  7. inspector_overlay/
  8. node_modules/
  9. scripts/
  10. test/
  11. third_party/
  12. v8/
  13. .clang-format
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.js
  17. .gitattributes
  18. .gitignore
  19. .gn
  20. .mailmap
  21. .npmignore
  22. .npmrc
  23. .style.yapf
  24. .stylelintignore
  25. .stylelintrc.json
  26. ARCHITECTURE.md
  27. AUTHORS
  28. BUILD.gn
  29. codereview.settings
  30. DEPS
  31. LICENSE
  32. OWNERS
  33. package-lock.json
  34. package.json
  35. PRESUBMIT.py
  36. README.md
  37. tsconfig.json
  38. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.

Source code

The frontend is available on chromium.googlesource.com.

Design guidelines

Please be aware that DevTools follows additional development guidelines.

Issue triage

The issue triage guidelines can be found in docs/triage_guidelines.md.

Workflows

Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.

Additional references

Source mirrors

DevTools frontend repository is mirrored on GitHub.

DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.

The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.

Getting in touch