Ingvar Stepanyan
b532f3f71f
When comparing filenames, PRESUBMIT didn't exclude files listed in .eslintignore from formatting, because .eslintignore contains forward slashes, but all the files are using native OS-level slashes, so any comparisons failed. This fixes it by normalising all paths found in .eslintignore. Change-Id: I9f5cd3cbf15b4b27677968747cf349cde2aed1b3 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1872596 Auto-Submit: Ingvar Stepanyan <rreverser@google.com> Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org>
Chrome DevTools frontend
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.
Getting Started (Standalone)
As standalone project, Chrome DevTools front-end can be checked out and built independently from Chromium.
Checking out source
Get depot_tools first.
mkdir devtools
cd devtools
git clone https://chromium.googlesource.com/devtools/devtools-frontend
gclient config https://chromium.googlesource.com/devtools/devtools-frontend --unmanaged
Build
cd devtools-frontend
gclient sync
gn gen out/Default
autoninja -C out/Default
Run in Chromium (from M79 onwards)
To run the production build, use
<path-to-chrome>/chrome --custom-devtools-frontend=file://$(realpath out/Default/resources/inspector)
To run the debug build (directly symlinked to the original unminified source files),
build both Chromium and DevTools frontend with the GN flag debug_devtools=true, and use
<path-to-chrome>/chrome --custom-devtools-frontend=file://$(realpath out/Default/resources/inspector/debug)
Getting Started (as part of Chromium)
DevTools frontend can also be developed as part of Chromium.
Follow instructions to check out Chromium.
DevTools frontend can be found under chromium/src/third_party/devtools-frontend/src/.
Build as part of Chromium
Refer to instructions to build Chromium.
To only build DevTools frontend, use devtools_frontend_resources as build target.
Integrate standalone DevTools into Chromium
Change your working directory to the integrated DevTools frontend:
cd path/to/chromium/src/third_party/devtools-frontend/src
Add standalone DevTools frontend as remote:
git remote add standalone file://path/to/devtools/devtools-frontend/
git fetch standalone
git checkout standalone/branch-of-your-choice
Hacking
- DevTools documentation: devtools.chrome.com
- Debugging protocol docs and Chrome Debugging Protocol Viewer
- awesome-chrome-devtools: recommended tools and resources
- Contributing to DevTools: bit.ly/devtools-contribution-guide
- Contributing To Chrome DevTools Protocol: docs.google.com
Useful Commands
npm run format-py
Formats your Python code using yapf
Note: Yapf is a command line tool. You will have to install this manually, either from PyPi through
pip install yapfor if you want to enable multiprocessing in Python 2.7,pip install futures
Development
- 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
- Test waterfall
NPM package
DevTools frontend is available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES2015 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
-
@ChromeDevTools on Twitter
-
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools