Rename DEBUG env var to DEBUG_TEST Currently, you cannot run tests in non-debug mode and turn on debug logging from Puppeteer that relies on https://www.npmjs.com/package/debug. Running `DEBUG=puppeteer.* ...` would also start the test runner in a debug and non headless mode. This CL renames the DEBUG variable that DevTools test runner relies on so that debug logging is independent from the debug mode we have for tests. Bug: none Change-Id: I8b8476f7c26c07eea1db29bfae74d4fb61afd42c Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2963755 Reviewed-by: Simon Zünd <szuend@chromium.org> Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Jan Scheffler <janscheffler@chromium.org> Commit-Queue: Alex Rudenko <alexrudenko@chromium.org>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Please be aware that DevTools follows additional development guidelines.
The issue triage guidelines can be found in docs/triage_guidelines.md.
Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.
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: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools