Repository files navigation

The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.

The frontend is available onchromium.googlesource.com. Check out theChromium DevToolsdocumentation for instructions toset up, use, and maintain a DevTools front-end checkout,as well as design guidelines, and architectural documentation.

• DevTools user documentation:devtools.chrome.com
• Debugger protocol documentation:chromedevtools.github.io/devtools-protocol
• Awesome Chrome DevTools:github.com/paulirish/awesome-chrome-devtools
• Contributing to Chrome DevTools:goo.gle/devtools-contribution-guide
• Contributing To Chrome DevTools Protocol:goo.gle/devtools-contribution-guide-cdp

DevTools frontend repository is mirrored onGitHub.

DevTools frontend is also available on NPM as thechrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may requiresome 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.

• @ChromeDevTools on Twitter
• Chrome DevTools mailing list:g/google-chrome-developer-tools
• File a new DevTools ticket:goo.gle/devtools-bug

There are a few options to keep an eye on the latest and greatest of DevTools development:

• FollowWhat's new in DevTools.
• FollowUmar's Dev Tips.
• Follow these individual Twitter accounts:@umaar,@malyw,@kdzwinel,@addyosmani,@paul_irish,@samccone,@mathias,@mattzeunert,@PrashantPalikhe,@ziyunfei, and@bmeurer.
• Follow tog/devtools-reviews@chromium.org mailing list for all reviews of pending code,andview the log, or follow@DevToolsCommits on Twitter.
• Checkoutall open DevTools tickets on crbug.com
• Use Chrome Canary and poke around the experiments.