Chrome DevTools frontend
This repository contains the client side of Chrome DevTools. It contains all the TypeScript and CSS code that runs the DevTools web app.
Source code and documentation
The source code is on [chromium.googlesource.com].
The [Chromium DevTools documentation] tells you how to do these tasks:
- [Set up] a DevTools frontend checkout.
- Use a DevTools frontend checkout.
- Maintain a DevTools frontend checkout.
Other documentation:
- DevTools user documentation: devtools.chrome.com
- Chrome DevTools Protocol documentation: chromedevtools.github.io/devtools-protocol
- A list of Chrome DevTools resources: github.com/paulirish/awesome-chrome-devtools
- How to contribute to Chrome DevTools: goo.gle/devtools-contribution-guide
- How to contribute to the Chrome DevTools Protocol: goo.gle/devtools-contribution-guide-cdp
Source mirrors
There is a mirror of the DevTools frontend repository on GitHub.
The DevTools frontend is also available on npm as the chrome-devtools-frontend package. The package does not supply CJS modules or ES modules. Thus, it can be difficult to use this package in other tools. For an example of how to use it, see this file.
The version number of the npm package (for example, 1.0.373466) is the
Chromium commit position of the latest frontend Git commit. The version number
increases with each Chromium commit. But we publish the package only
approximately one time each day.
Contact us
- Follow [@ChromeDevTools] on X (previously Twitter).
- Send a message to the Chrome DevTools mailing list: [g/google-chrome-developer-tools]
- Report a new DevTools bug: [goo.gle/devtools-bug]
Get the latest news
To get the latest news about DevTools development, do one or more of these steps:
- Read [What's new in DevTools].
- Read [Umar's Dev Tips].
- Follow these accounts on X:
- Join the [g/[email protected]] mailing list. This list shows all
- Read the [commit log], or follow [@DevToolsCommits] on X.
- See [all open DevTools bugs] on crbug.com.
- Use Chrome Canary and try the experiments.