commit | d53ca9807f416e58f6611f7c01cf4cbff9004279 | [log] [tgz] |
---|---|---|
author | Maksim Sadym <sadym@chromium.org> | Tue Sep 22 08:12:10 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Sep 22 10:24:34 2020 |
tree | e3319b77cc6375acf94059b45b6dc78564021de8 | |
parent | a8aa0a8f5d264e2de11cc49ff4c95f7e15d92705 [diff] |
Respect additional arguments in npm targets Make following targets respect additional arguments, so that `--chrome-binary=[LOCATION] --chrome-features=[FEATURES]` can be used. * `auto-debug-e2etest` * `auto-debug-unittest` * `auto-e2etest` Bug: 1130513 Change-Id: I416dd08cc38597355d98ec43029e639716762296 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2422946 Reviewed-by: Mathias Bynens <mathias@chromium.org> Commit-Queue: Maksim Sadym <sadym@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 here.
Instructions to set up, use, and maintain a DevTools frontend checkout can be found here.
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