Turtle
38c7a9fbf4
* feat(release): publish package source, declaration maps, and documentation Every release member publishes its TypeScript source and the declaration maps that resolve into it, and @deepseek-ai/dsh publishes the repository Markdown documentation staged from docs/ at prepack time. The ./src/* export most members already declared now resolves for an installed consumer, and a consumer editor follows a declaration to the implementation. Bundled JavaScript maps stay unpublished; the vendored family and the Desktop runtime file policy are unchanged. Rationale: .agents/notes/implemented/process/2026-10-08-published-source-and-docs.md * feat(release): publish JavaScript maps and compress bundles Every emitted JavaScript map ships beside the bundle it describes, and the workspace build and the client preset compress bundles without mangling identifiers. The documentation payload now mirrors the website publication manifest and is removed again by `postpack`; Desktop and the Python executable exclude the published source, documentation, and maps; `clean` removes a staged copy. Typert's publication contract gains the Remote declaration map. * fix(release): keep node bundles readable for the worker image The browser worker image lowers `yield*` only as a whole statement and rewrites `for await` loops by their source layout, so compressed node-side entries either fail that lowering or lower to unparseable code. Only the browser bundles keep compression, which removes about a third of their text. The bundle-purity assertion now matches the module-loader call regardless of the quote style compression picks, and the release-pack fixture exercises the installed package's new documentation requirement. * feat(release): publish the whole documentation tree `@deepseek-ai/dsh` copies `docs/` in full instead of the website's page set: the maintainer documents, the generated migration records, the translation guidelines, and the `*.i18n.yaml` consistency records ship with the installed package, so the documentation's own links resolve without a checkout. * feat(release): publish the upgrade guides with the documentation The staged documentation keeps the website's page set and adds every `docs/upgrade-guide/` document, which is what an installed reader consults when a released change breaks something. The rest of the maintainer tree stays out. * test(release): expect source and maps in master's new payload cases * feat(release): keep installed docs and source readable in Desktop Desktop keeps the published src/ and docs/ trees inside app.asar, and every model shell call receives DSH_INSTALL_DIR and DSH_NODE_EXECUTABLE so an agent can read them through Electron's Node mode. Staging also generates docs/upgrade-guide/README.md, an index of the upgrade guides grouped by the release they upgrade from. Minified client bundles print string literals with backticks: the worker image packer now recognizes those chunk requests, client license banners are prepended after minification so their text survives, and the affected artifact tests accept either quote. * test(desktop): read archived docs through the Windows PowerShell form Regenerate the config catalog for the shifted shell-env source line. * test(desktop): wait for the GUI-subsystem Electron process from PowerShell * build(release): publish source and maps from the message-quotes package * build(release): publish source and maps from packages new on master * build(release): publish source and maps from the tool-office package
description, kind
| description | kind |
|---|---|
| Cross-runtime UUID generation for maintainers replacing secure-context-only crypto.randomUUID calls. | package-library |
dsh-util-crypto
English | 中文
Summary
Zero-dependency browser-safe UUID and byte-encoding helpers. UUID minting uses crypto.getRandomValues, the one random primitive every shipped context provides. crypto.randomUUID is a secure-context Web API: a page or worker served over plain HTTP on a LAN address (the browser preview deployment) has no such method, so code that must run there cannot call it. The repository-wide no-restricted-properties lint rule points crypto.randomUUID callers here; Node-only code importing randomUUID from node:crypto stays as it is.
Table of Contents
Use this package
It is a library, not a service or plugin: no ctx, registers nothing, holds no state.
API
import { bytesToBase64, randomUUID, type Uuid } from '@deepseek-ai/dsh-util-crypto'
| Export | Role |
|---|---|
bytesToBase64(data) |
Canonical base64 for a byte array, encoded in bounded chunks. |
randomUUID() |
Random RFC 9562 v4 UUID string, minted from crypto.getRandomValues. Drop-in for crypto.randomUUID(). |
Uuid |
The five-group UUID string type, matching crypto.randomUUID's declared return shape. |
Model Experience
Indirectly, through consumers that mint request, session, and attachment identifiers with it, none of which enter prompts as semantic content.
KV Cache effect
No direct invalidation; identifier-minting consumers own any request changes.
Known Limitations and Deferred Work
- v4 only — no other UUID versions, namespaces, or parsing; consumers needing more should take a real UUID dependency.
- Uniqueness is probabilistic — 122 random bits, the same guarantee
crypto.randomUUIDgives; nothing here detects collisions.
Dev Note
Working context for maintainers — click to expand
None.