RPP: Fix overwriting of default config; simplifying config. Discovered this investigating the failures of my JS Samples CL/revert: https://ci.chromium.org/ui/p/devtools-frontend/builders/ci/Stand-alone%20Win/12265/overview I inadvertently mutated the default config in a test. Unfortunate it was so easy to do that and not trigger alarms. This CL has safeguards. We overhaul the configuration so its a flat object that Readonly<> will help enforce. Meanwhile, we can also simplify config consumption quite a bit. Bug: 1477187 Change-Id: I783edfa3acfdc8c22143140cc967b57294a6eea7 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5528502 Commit-Queue: Paul Irish <paulirish@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Auto-Submit: Paul Irish <paulirish@chromium.org>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
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.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools