@tssuite/dna-ts
v1.1.1
Published
DNA for all of our TypeScript projects - TS-specific configs and docs on top of base_dna, inherited via gg_dna.
Keywords
Readme
dna-ts
The DNA for all of our TypeScript projects. Builds on base_dna and adds the TypeScript-specific layer, inherited via gg_dna:
dna/dot-vscode/settings.overrides.json— TS/ESLint editor settings merged into the base settingsdna/dot-vscode/extensions.overrides.json— TS extension recommendations (array join)dna/dot-vscode/typescript.code-snippets— workspace snippets (license header, test skeleton)dna/dot-claude/skills/review/SKILL.md— the review skill with the kebab-case convention filenames a TypeScript project instantiatesdna/test/dna/dna.spec.ts— the DNA wrapper spec shipped to TS consumers (instantiated astest/dna/dna.spec.ts)
Dotfiles carry a dot- prefix inside dna/ and lose it when
instantiated (dna/dot-vscode/… → .vscode/…). Without the escape
dart pub publish drops them, and the layer would reach pub consumers
incomplete.
Usage
pnpm add -D dna-ts @tssuite/helix-js
gg_dna initThe placed spec instantiates and verifies the DNA on every test run
(base_dna is pulled in transitively). The engine runs via
@tssuite/helix-js — the gg_dna engine compiled to WebAssembly.
Development
role: "dna" in dna/_dna.json: the dna/ folder is authored by hand.
The repo instantiates its own DNA — run pnpm test after changes; commit
first (a file the DNA would overwrite must not carry uncommitted work).
During development gg_localize_refs points the @tssuite/dna-base
dependency at the local base_dna checkout; the DNA config itself never
holds paths.
