Files
deepseek-harness/packages/util/package-manifest

description, kind
description kind
Shared TypeScript declarations for package.json.dsh metadata, usable by boot, client, build, and external packages. package-library

@deepseek-ai/dsh-package-manifest

English | 中文

Summary

Use DshManifest to type a package's Harness metadata, or a member type such as DshClientManifest for one declaration. Boot, client, build, and external packages import the same types; each reader owns JSON validation and default resolution.

Table of Contents


Use this package

Import from the package root. Use a development dependency when only checking your own source; use a production dependency if your published declarations reference these types.

import type { DshClientManifest, DshManifest } from '@deepseek-ai/dsh-package-manifest'

const client: DshClientManifest = { platform: 'web' }
const dsh: DshManifest = {
  bundle: { patch: './cordis.patch.yml' },
  client,
}

DshManifest describes bundle, profile, client, configTrees, sessionFormatMigration, and moduleFallback, not the surrounding npm manifest. moduleFallback is launcher-generated metadata and is not an author configuration entry. TypeScript checks this object and erases import type during compilation; JSON files cannot import types, and this example does not write a package.json. See src/types.ts for the declarations.


Understand the implementation

Implementation internals — click to expand

The package root only re-exports declarations from src/types.ts. No runtime invariant companion is published because the package has no runtime state or independently observable relationships.


Further Exploration

Model Experience

None, as this package only exports types.

KV Cache effect

Type declarations add no model input, so provider cache reuse is unaffected.

Known Limitations and Deferred Work

  • Static typing only. These declarations do not validate JSON, check file existence, or supply defaults. configTrees serves the experimental image packer, and sessionFormatMigration is discovered only for workspace migration packages; declaring them does not register external plugin behavior.

Dev Note

Working context for maintainers — click to expand

None.