imccyu
e4410b2764
The client tsdown presets found a package's own manifest by name: a glob of every packages/*/*/package.json, parsed until the name matched. tsdown's native config loader imports each package config without module cache, so the module-level cache never hit and all 82 configs repeated the glob (40-125 ms each) synchronously on tsdown's main thread, where it delayed every other package build. It was 34.5% of the client pass's main thread. - clientBundle, staticLinked and clientLibrary take the package directory (import.meta.dirname at every call site) and read <dir>/package.json once; the package name, loader id and externals come from that manifest. - A missing, unreadable or nameless manifest throws an actionable error. - The glob, the name search and the module-level caches are removed. tsdown client pass 12.78 s -> 8.73 s (median of 3 interleaved runs each, -31.7%); all 11,566 lib outputs byte-identical; all 82 configs resolve the same externals and banners. Refs #5852
description, kind
| description | kind |
|---|---|
| The shell executor's settings page on the dsh web client's Plugins page: the command timeout and the per-stream output cap of the shell namespace. | package-reference |
@deepseek-ai/dsh-client-ui-settings-shell
English | 中文
Summary
Open Plugins in the sidebar and select Shell in the Official group to set how long one command may run and how much of each output stream stays in memory. The page stages what is typed and writes it only on save, marks the values the user overrode, and offers to reset each back to the deployment's default. The page exists while the Host serves the shell namespace, so a deployment without a local shell executor shows no trace of it.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
The Shell card in the Official group opens the page. Command timeout (ms) ends a command that runs longer; Output cap per stream (bytes) spills output beyond it to a temporary file. Both render the effective value — the user's override over the composed default — and a field the user overrode carries an Overridden badge with Reset to default beside it. Nothing is written until Save; leaving the page drops the drafts, an empty field saves as a reset, and text that is not a number blocks the save and says so under the field.
Understand the implementation
Implementation internals — click to expand
The Host half is an empty apply, present only so the package holds a Loader row the client module system serves the browser half for. The browser half binds the composed shell executor entry (bash-sandbox off Windows, pwsh-sandbox on it) through ctx.configForms.get, keeps the staged form in ShellCardController over the shared SettingsFormModel of ui-primitives, and registers ShellCard into the Plugins page's plugins.item slot through ctx.configForms.whileServed, which registers while the Host serves either entry and withdraws when it stops. The page's copy lives in this package's settings.shell dictionary; the SettingsForm frame takes its copy as props.
Further Exploration
- ui-plugin-manager — the Plugins page and the
plugins.itemslot the page registers into. - ui-settings — the settings scope and the served-namespace watch the page rides.
- ui-primitives — the settings form model and fields the page renders.
- bash-local — the executor that registers the
shellnamespace.
Model Experience
None, as the package is a browser-side settings surface that registers no model surface.
KV Cache effect
None; this package neither assembles nor sends a provider request.
Known Limitations and Deferred Work
- The page follows the composed executor — the POSIX and PowerShell executor families share the
shellnamespace because a host composes exactly one of them, so the served schema differs by platform (PowerShell addspwshPath) while the page edits the same two fields on both.
Dev Note
Working context for maintainers — click to expand
None.