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 |
|---|---|
| React and Slot adapters for Session Controller lists, interaction state, and per-session context. | package-reference |
@deepseek-ai/dsh-client-ui-session
English | 中文
Summary
Use this package to expose Session catalog, retain information, and unified UI status through standard Slot hooks. It materializes per-SessionBinding hooks and props, while SessionProvider can inherit an outer binding or bind an explicit SessionReference. It owns process-local pending-interaction and completion-reminder policy without owning Controller transport, history, or references.
Running status comes from Host list baselines or status events. Subagent catalog rows and retained subagent fallback rows do not establish running status; main view references still acknowledge completions.
Table of Contents
Model Experience
None, as this package adapts browser-side Session state and registers nothing model-facing.
KV Cache effect
None; Session selectors and Slot scopes do not assemble model requests.
Known Limitations and Deferred Work
- Pending interactions are process-local projections — the owning Remote waterfall must replay an outstanding request after a browser reconnect.
Dev Note
Working context for maintainers — click to expand
None.