Catch broken code examples in documentation before they confuse readers.
See type errors directly inside Markdown files while writing docs, like in a regular code editor.
Run documentation checks automatically in CI so pull requests fail on outdated snippets.
Keep multi-package monorepo documentation examples resolving correctly without manual path setup.
| alemtuzlak/kiira | blazeup-ai/pi-insights | deepelementlab/jupyter-studio | |
|---|---|---|---|
| Stars | 49 | 49 | 49 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | easy | easy |
| Complexity | 2/5 | 2/5 | 2/5 |
| Audience | developer | developer | data |
Figures from each repo's GitHub metadata at analysis time.
Needs a TypeScript config pointed at your docs plus your project's real type definitions.
Kiira is a tool that checks whether the TypeScript and JavaScript code examples in your Markdown documentation files actually work against your real project. When documentation is written or updated, it is easy for code snippets to fall out of sync with the actual API: imports that no longer exist, function names that changed, or options that were removed. Kiira extracts every code block from your Markdown files, runs them through TypeScript's type checker using your project's real type definitions, and reports any errors back on the exact line where the broken code block appears. The tool has three interfaces. A command-line tool called kiira check scans your documentation files and prints type errors. A Visual Studio Code extension shows error squiggles directly inside Markdown files as you write them, the same way errors appear in regular code files. A GitHub Actions composite action lets you run the same checks automatically in a continuous integration pipeline, with output formatted as GitHub annotations. For code examples that span multiple fences (for instance, a tutorial that declares a variable in one block and uses it in the next), you can tag related snippets with a shared group identifier so Kiira treats them as a single module. Kiira can also detect when ungrouped snippets would resolve each other's errors and suggest the grouping for you, with a flag to write the tags automatically. In monorepos with multiple packages, Kiira discovers the workspace structure from pnpm, npm, or yarn configuration and maps internal package names to their source locations automatically. This means documentation that imports from your own packages resolves without manually configuring path aliases. Per-file configuration overrides let you specify different JSX runtimes for documentation covering multiple frontend frameworks. If a code block is tagged as ts but actually contains JSX syntax, Kiira detects the mismatch, still type-checks it correctly, and can rewrite the tag with the fix flag. Setup requires installing the kiira npm package, creating a TypeScript configuration file pointing at your documentation, and optionally adding a Kiira configuration file to specify which files to include and how to resolve packages.
A tool that type-checks the code examples inside your Markdown docs so they never silently break.
Mainly TypeScript. The stack also includes TypeScript, JavaScript, VS Code Extension.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.