commit | 867b0b44217cacabd5362410590a096e1a010194 | [log] [tgz] |
---|---|---|
author | Benedikt Meurer <bmeurer@chromium.org> | Thu Apr 17 16:31:19 2025 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 21 10:35:05 2025 |
tree | c9650cb2895c8906afb25f83195efbb592df6ec3 | |
parent | 9337b1268837c462a92953e88458e66632db6871 [diff] |
[npm] Produce more readable build error messages. The `npm run build` and `npm start` were producing quite messy error messages, which are hard to parse, and the `esbuild` and `tsc` error message format was also (naturally) different. This change adjusts the error messages to always report in the `tsc` format (which is well understood and supported by IDEs and tools). It also removes the unnecessary clutter from the error messages and simplifies it to basically this (for `tsc`) ``` ✖ TypeScript compilation failed for `Debug' front_end/panels/timeline/components/insights/Checklist.ts(46,1): error TS1128: Declaration or statement expected. front_end/panels/timeline/components/insights/Checklist.ts(46,8): error TS1434: Unexpected keyword or identifier. front_end/panels/timeline/components/insights/Checklist.ts(46,8): error TS2304: Cannot find name 'TableDataRow'. front_end/panels/timeline/components/insights/Checklist.ts(48,3): error TS2552: Cannot find name 'overlays'. Did you mean 'Overlays'? front_end/panels/timeline/components/insights/Checklist.ts(48,12): error TS1109: Expression expected. front_end/panels/timeline/components/insights/Checklist.ts(48,14): error TS1361: 'Overlays' cannot be used as a value because it was imported using 'import type'. front_end/panels/timeline/components/insights/Checklist.ts(48,32): error TS2339: Property 'TimelineOverlay' does not exist on type 'typeof import("/usr/local/google/home/bmeurer/Projects/devtools/devtools-frontend/out/Debug/gen/front_end/panels/timeline/overlays/OverlaysImpl")'. front_end/panels/timeline/components/insights/Checklist.ts(48,48): error TS1011: An element access expression should take an argument. front_end/panels/timeline/components/insights/Table.ts(26,71): error TS1005: ',' expected. front_end/panels/timeline/components/insights/Table.ts(26,71): error TS2304: Cannot find name 'a'. front_end/panels/timeline/components/insights/Table.ts(26,74): error TS2345: Argument of type 'RegisteredFileStrings' is not assignable to parameter of type 'string'. front_end/panels/timeline/components/insights/Table.ts(66,39): error TS2554: Expected 0-1 arguments, but got 2. ``` and this (for `esbuild`): ``` ✖ TypeScript compilation failed for `Default' front_end/panels/timeline/components/insights/Checklist.ts(46,7): error TS0666: Unexpected "TableDataRow" front_end/panels/timeline/components/insights/Table.ts(26,70): error TS0666: Expected ")" but found "a" ``` Bug: 411328609 Change-Id: Ic0be7780a91810386e38997c7237210aa69f63dd Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6469693 Reviewed-by: Nikolay Vitkov <nvitkov@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@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.