Update translations for M105 Bug: 1350068 Change-Id: I34f248db757f97d0cca81c9137d83d9e0f95a755 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3810333 Auto-Submit: Changhao Han <changhaohan@chromium.org> Commit-Queue: Ergün Erdoğmuş <ergunsh@chromium.org> Reviewed-by: Ergün Erdoğmuş <ergunsh@chromium.org> Commit-Queue: Changhao Han <changhaohan@chromium.org> (cherry picked from commit 453aa9a9b11b4dcd612a807993de8d59efb41d86) Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3810247 Reviewed-by: Simon Zünd <szuend@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