Development
This guide covers the development environment setup and build process for Chrome Remote DevTools.
Development Commands
Building DevTools Frontend
The DevTools UI is based on a fork of Chrome DevTools frontend. To build it, you need to have depot_tools installed.
Prerequisites
-
Install depot_tools: Follow the depot_tools setup guide.
-
Ensure depot_tools is in your PATH: The
gclient,gn, andautoninjacommands should be available.
Build Steps
-
Navigate to devtools directory:
-
Sync dependencies:
This will download all required dependencies for devtools-frontend.
-
Generate build configuration:
-
Build DevTools:
Alternatively, you can use npm:
-
Build artifacts location: The built files will be in
devtools/devtools-frontend/out/Default/gen/front_end.
Fast Build Options
For faster iteration during development, you can skip type checking and bundling:
Or use npm with the fast-build target:
Notes
- The first build may take a while as it downloads dependencies and compiles everything.
- Subsequent builds are incremental and much faster.
- The build uses
Defaultas the target by default. You can specify a different target with-t <name>. - For development, you typically don't need to rebuild DevTools unless you're modifying the DevTools frontend code itself.
Server Log Configuration
Server logs are disabled by default to reduce console noise. Enable them using environment variables:
Note: Logs are automatically disabled in production builds.