Commit Graph
12 Commits
Author SHA1 Message Date
Benedikt Meurer 6b1b791739 [npm] Port npm start to JavaScript.
There's no point in writing this one script in Python. It's much better
to have it in JavaScript, just like `npm run build`.

Bug: 404192426
Change-Id: Ic19eaeb5b1d97ca750ae4253963b8434072d00fd
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6387801
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Nikolay Vitkov <nvitkov@chromium.org>
2025-03-25 05:33:21 -07:00
Benedikt Meurer ec23749325 [docs] Add more documentation for npm run build.
Specifically document the Linux specific limits for `inotify` which
one can easily run into when combining `npm run build -- --watch`
and VS code.

Bug: 404192426
Change-Id: Idf301cb2e773325b2d299e61e879f85541551aa4
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6376063
Reviewed-by: Nikolay Vitkov <nvitkov@chromium.org>
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
2025-03-20 10:51:03 -07:00
Benedikt Meurer eabb1f3605 [npm] Add watch mode to npm run build and npm start.
This adds a new script for `npm run build`, which supports a `--watch`
argument, to automatically re-build whenever source files change. It
also hooks this up to `npm start`, which to automatically rebuild in
the background while Chrome is running.

Bug: 404192426
Change-Id: I90ee3ea81312bcfff9470ab8c62d38608e4e9a71
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6367220
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Mathias Bynens <mathias@chromium.org>
Reviewed-by: Mathias Bynens <mathias@chromium.org>
2025-03-19 11:01:21 -07:00
Benedikt Meurer f395cc3765 [npm] Fix enabled/disabled features.
Pass only a single `--disable-features=` / `--enable-features` CLI
flag to Chrome binary.

Bug: 404192426
Change-Id: I858f87b41e9328cb0e3b9a5c7e16a0f57a73be53
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6367217
Commit-Queue: Mathias Bynens <mathias@chromium.org>
Reviewed-by: Mathias Bynens <mathias@chromium.org>
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
2025-03-18 07:28:52 -07:00
Benedikt Meurer 6b5dba97f0 [npm] Add initial npm start script.
This adds an initial version of the `npm start` script, which builds the
DevTools front-end and launches either CfT or Chrome Canary binary with
the custom DevTools front-end, passing appropriate flags to enable or
disable certain experimental features.

Bug: 404192426
Change-Id: Ia7bcbf8cb5f93bcf455e59964a488480e8ec1fff
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6367034
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
2025-03-18 03:34:36 -07:00
Benedikt Meurer d604ae2d17 [unified-css] Rename .css.legacy.js to .css.js.
This also removes the logic to generate the constructed style sheet
`.css.js` files, and with it the solution for CSS hot reloading (which
never worked for the "legacy CSS" approach).

Bug: 391381439
Change-Id: I7492f7d1b55dcb4f071a7c55974565a79dbbdb17
Doc: https://goo.gle/devtools-unified-css-design
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6218494
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Nikolay Vitkov <nvitkov@chromium.org>
2025-01-31 07:13:57 -08:00
Mathias Bynens 5517d77d5a Document that Chrome Canary is is_chrome_branded
- Chrome for Testing releases are built with `is_official_build` + `is_chrome_for_testing_branded`.
- Regular Chrome releases are built with `is_official_build` + `is_chrome_branded`.
- Chromium builds usually have none of these GN args set.

Any features conditional on `is_chrome_branded` are thus not supported in Chromium nor in CfT.

Bug: none
Change-Id: Ia8ecac55d93e2cca9abcb4fa3220293858cd7e17
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6021663
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Auto-Submit: Mathias Bynens <mathias@chromium.org>
2024-11-15 14:13:21 +00:00
Connor Clark 190b4dfc62 Fix Mac instructions for running with pre-built chrome
Bug: none
Change-Id: I94d1d9a4484df77f0757f92065f6ac8c0b8f5cdf
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5319228
Reviewed-by: Paul Irish <paulirish@chromium.org>
Commit-Queue: Connor Clark <cjamcl@chromium.org>
2024-03-14 22:55:24 +00:00
Alex Rudenko 458f24cec9 Update Windows docs
Bug: none
Change-Id: I127234975fce1772ba3495f85e0a19a3c164edb3
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5103213
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Alex Rudenko <alexrudenko@chromium.org>
2023-12-08 12:18:14 +00:00
Mathias Bynens d3a5ea3ce3 [docs] Recommend --disable-infobars for local testing
For local testing, any automation infobars as well as the Chrome for
Testing-specific infobar aren’t usually desired.

Now that CfT reintroduced the `--disable-infobars` CLI flag, we can
recommend its use for this purpose.

Bug: chromium:1476789
Change-Id: Ic174f62d9df3846e891f3a420e0ecca75295bad2
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5077246
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Auto-Submit: Mathias Bynens <mathias@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
2023-11-30 14:00:41 +00:00
Ergun Erdogmus 8542c3e991 Add documentation for watch script
Bug: none
Change-Id: Ia7b1ee01257b6ed63311d3fa1cb1f85bec46e2b9
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5002180
Reviewed-by: Simon Zünd <szuend@chromium.org>
Commit-Queue: Ergün Erdoğmuş <ergunsh@chromium.org>
2023-11-07 10:57:56 +00:00
Benedikt Meurer 70710c8820 [docs] Streamline documentation.
Previously we had a lot of documentation bundled in the `workflows.md`
file, which wasn't necessarily obvious to new users. The getting the
code documentation now lives in a dedicated file `get_the_code.md`,
which is also directly linked from the toplevel `README.md`, since
that's what developers are looking first.

It also rearranges the rest of the project documentation a bit to move
the most important things to the top, add [TOC]s everywhere and
streamlines the documentation around (3rd party) dependencies, as well
as updating the documentation on testing.

Bug: none
Change-Id: I7b5d9121c7f1137eeff7a4ff159816908ef10705
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4931037
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Auto-Submit: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
2023-10-12 12:15:09 +00:00