[Rush] Add rush-serve plugin dashboard UI and config updates#5893
[Rush] Add rush-serve plugin dashboard UI and config updates#5893mojaza wants to merge 1 commit into
Conversation
|
@mojaza please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
| // Copyright (c) Microsoft Corporation. All rights reserved. Licensed under the MIT license. | ||
| // See LICENSE in the project root for license information. | ||
|
|
||
| // @ts-nocheck |
There was a problem hiding this comment.
remove ts-nocheck, we need this file to be checked.
There was a problem hiding this comment.
Ah, I removed it on a different codespace which hasn't been staged. I just removed it and made the file types safe in this file.
| // @ts-nocheck | ||
|
|
||
| // Removed in-page log panel; logging now goes directly to devtools console | ||
| const statusPill = document.getElementById('status-pill'); |
There was a problem hiding this comment.
split off the dashboard.ts into smaller scoped modules.
try to componentise the web app. for example, the top bar can live in a separate file and have it's own scoped CSS module
There was a problem hiding this comment.
try to keep the state and mutation logic separate from rendering
Summary
This PR adds a built-in dashboard for the Rush serve plugin so developers can monitor and control watch-mode execution from a browser without creating a separate client.
The change introduces dashboard frontend assets, serves them through the plugin, and documents how to configure and open the dashboard route.
Details
Added a dashboard UI with:
Other changes:
Design notes
Considered keeping the dashboard as an external sample app.
Chose an in-package dashboard to make onboarding easier and reduce setup friction.
Compatibility and performance
Backward compatibility is preserved; changes are additive.
Existing plugin configuration continues to work.
Runtime impact is expected to be minimal and mostly limited to static asset serving during watch-mode usage.
How it was tested
TBD
Impacted documentation