[sources] Gracefully ignore history items with invalid resource type names. This makes DevTools front-end more robust with respect to future additions (and potential removals) of resource types. It also makes it less painful to experiment with new resource types locally. Bug: chromium:1408032, chromium:1408033 Change-Id: I446e43a0b4fa70971faaae2016ef803695f5235d Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4218950 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Kim-Anh Tran <kimanh@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Kim-Anh Tran <kimanh@chromium.org> (cherry picked from commit be826f50274c2274965373199a6b33df252267c6) Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4337918
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
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