[devtools_pre_built] Expose -dts sub-target alias and add prebuilt test fixture
Update devtools_pre_built to copy assets to both target_gen_dir and the
intermediate tsc directory using two separate copy actions, and expose a
${target_name}-dts group alias so that ts_library_split and
devtools_entrypoint_split targets can depend directly on prebuilt
third-party packages. Also adds an integration test fixture and
consolidates build test fixtures under scripts/build:tests.
Bug: 547522497
Change-Id: Ieb25d4928061dfa1828dfe4f673c5eae56ea6863
TAG=agy
CONV=f4ebce7e-f209-48d0-be3f-7c9dbea28500
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8274751
Reviewed-by: Alex Rudenko <alexrudenko@chromium.org>
Commit-Queue: Simon Zünd <szuend@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.