commit | 0ceb465d1c02811a5ba30edda84377c94db2b0d3 | [log] [tgz] |
---|---|---|
author | Tim van der Lippe <tvanderlippe@chromium.org> | Thu Jan 06 13:23:36 2022 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 06 15:06:40 2022 |
tree | 801c578e01b088461d417c4cb160599fcf63bdc8 | |
parent | 92b451ffb189d0d5a3b49fc92a47a6fcab485547 [diff] |
Update ESLint and plugin packages R=jacktfranklin@chromium.org Bug: none Change-Id: If1b2420ba6e1c100c3d6b2013815ff1a555ea987 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3369367 Auto-Submit: Tim Van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@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