[console] Support arbitrary private fields for autocompletion. As of https://crrev.com/c/4020267 it is possible to access private fields of objects outside of the class scope via debug-evaluate, so we no longer need to restrict the autocompletion source for private fields in the DevTools front-end. Fixed: chromium:1483848 Bug: chromium:1381806 Change-Id: I3d762ad4001c70ce4fc8ccb087cac9014aae588b Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4871997 Commit-Queue: Benedikt Meurer <[email protected]> Reviewed-by: Philip Pfaffe <[email protected]> Auto-Submit: Benedikt Meurer <[email protected]> Commit-Queue: Philip Pfaffe <[email protected]>
The client-side of the Chrome DevTools, including all JS & 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: [email protected]
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools