Add helpers to launch eval base apps Introduces setupAndRunEvalApp and stopEvalApp in test/ai_evals/helpers/ai_eval-helpers.ts to locate and parse task.textproto configuration, execute prerequisite setup commands in base app directories, and spawn the server process group. Key changes: - parseTaskTextproto parses base_app and task_entry_point. - setupAndRunEvalApp configures npm environment overrides to permit platform optional binaries, caches existing node_modules, and spawns the detached server process group. - waitForProcessOutput reactively waits for startup output matching a target pattern using stream events. - stopProcess and stopEvalApp cleanly terminate the process group via SIGTERM with a SIGKILL fallback. - Adds test/ai_evals/network/failing-request.test.ts verifying failing-request eval app startup. - Registers network target in test/ai_evals/BUILD.gn. Bug: 523193113 Change-Id: I14747bf7b3d430904af25620844d68d4a8ab6557 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8361297 Auto-Submit: Kateryna Prokopenko <kprokopenko@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 TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools 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.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.