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 |
|---|---|
| Control Session-log upload with DeepSeek API requests from General settings. | package-reference |
@deepseek-ai/dsh-client-ui-settings-session-log
English | 中文
Summary
Use Upload Session Log when using the official model API above the version number in Settings → General to control Session-log upload with DeepSeek API requests. The switch shows the accepted Host setting and saves each change immediately. It appears only while the Host exposes the upload setting; read-only clients cannot change 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 Web bundle mounts this companion. Its switch edits the Host plugin's enabled field through the shared configuration form. A save failure keeps the accepted value and shows a toast that survives closing Settings. See Session-log upload for request timing, resumed uploads, and the separate OpenTelemetry setting.
Understand the implementation
Implementation details — click to expand
The companion contributes a settings.general.item row while session-log-deepseek is served and a shell.overlay toast for mutation outcomes. The shared form owns persistence and reconnect synchronization; the companion owns only pending-write state and localized notices.
Further Exploration
- Settings forms — accepted Host values and ordered writes.
- Session-log upload — request contribution and acceptance tracking.
- Web Client — plugin composition and settings placement.
Model Experience
None, as this browser preference contributes no model-visible content.
KV Cache effect
None; the setting controls request metadata outside model input.
Known Limitations and Deferred Work
- The row is unavailable when the Host does not expose the
session-log-deepseeknamespace.
Dev Note
None.