A local-first structured text parser and visualizer.
Kata is a worker-first, offline-capable PWA for parsing, inspecting, comparing, and exporting structured text directly in the browser. It is designed for mixed audiences: fast enough for performance-sensitive workflows, but approachable enough for developers who need a self-contained tool with no backend dependency after load.
Overview
Kata parses, visualizes, diffs, and exports structured text entirely in-browser. The application is built around Web Workers, virtualized rendering, and progressive file handling so that large documents remain responsive without requiring a backend service.
Capabilities
| Capability |
Details |
| Input formats |
JSON, JSONC/JSON5, YAML, TOML, INI, Markdown, XML, XAML, CSV, TSV, and plain text |
| Export formats |
Every input format except JSONC, which exports as JSON |
| Views |
Tree, Raw, and Diff |
| Local file workflows |
Manual file mode and workspace folder mode |
| Search and analysis |
Indexed search, node references, and diff inspection |
| Runtime model |
Dedicated parse and export workers |
| App shell |
Installable PWA with offline caching |
Requirements
Use the project with the runtime and platform expectations below.
| Requirement |
Version |
Notes |
| Node.js |
20+ |
Required for local development and builds |
| npm |
10+ |
Used by the existing scripts and workflows |
| Browser |
Chromium-based recommended |
Full workspace file features depend on the File System Access API |
Dependencies
| Category |
Packages |
| UI |
preact, @preact/signals |
| Parsing and formats |
yaml, smol-toml, ini, micromark, fast-xml-parser |
| Build |
vite, @preact/preset-vite, typescript |
| PWA |
vite-plugin-pwa |
| Performance tooling |
lighthouse, chrome-launcher, chrome-remote-interface |
Installation
Quick Start
Start the local development server:
Common follow-up workflows:
npm run build
npm run preview
npm run check
npm run perf:report
Architecture
Kata follows a worker-first architecture with a thin Preact UI layer, virtualized rendering, and base-aware PWA configuration for local and GitHub Pages deployments.

Source: docs/diagrams/architecture.mmd
Design Principles
- Keep main-thread blocking low by pushing heavy parsing and export work into workers.
- Favor local-first workflows with no required backend after the app shell loads.
- Render only what is visible so large documents remain interactive.
- Keep deployment base paths configurable so the same app works locally and on GitHub Pages.
Kata treats performance as a first-class project concern. The latest generated summary is available in reports/performance/latest.md.
| Budget |
Status |
Actual |
Target |
| First render |
PASS |
57.03 ms |
<= 100 ms |
| View switch |
PASS |
2.3 ms |
<= 50 ms |
| Expand/collapse |
PASS |
0.87 ms |
<= 16 ms |
| Initial bundle gzip |
PASS |
27,319 B |
<= 51,200 B |
| Long tasks over 50 ms |
PASS |
0 |
0 |
| Lighthouse mobile score |
PASS |
100 |
>= 90 |
| Lighthouse desktop score |
PASS |
90 |
>= 90 |
Lighthouse Summary
| Metric |
Mobile |
Desktop |
| FCP |
1316.4 ms |
1314.26 ms |
| LCP |
1578.06 ms |
1574.42 ms |
| TBT |
11.67 ms |
10.17 ms |
| CLS |
0 |
0 |
Detailed artifacts:
Development
Use the existing npm scripts and GitHub workflows to keep the repo in a releasable state.
npm run dev
npm run check
npm run build
npm run perf:report
Workflow Notes
npm run check runs the TypeScript build checks.
npm run build produces the production Vite bundle.
npm run perf:report builds, previews, audits, and refreshes tracked performance artifacts.
- The CI workflow runs type-checking and build validation on pushes and pull requests.
Deployment
Kata is deployed to GitHub Pages and uses a configurable app base so the same build can run from / locally and from a repository path in hosted environments.
Troubleshooting
Use these constraints when local behavior does not match the hosted app or when file access features appear limited.
Note: Workspace folder mode depends on browser support for the File System Access API, so Chromium-based browsers provide the most complete experience.
Note: The performance report workflow needs a Chrome executable. In CI this is provided by browser-actions/setup-chrome; locally you may need to set CHROME_PATH.
Links
Contributing
- Create a branch from
main for the change.
- Run
npm run check and npm run build before opening a pull request.
- Run
npm run perf:report when the change affects runtime or bundle behavior.
- Open a pull request with enough context to review product, architecture, and performance impact.
Copyright © 2026 Corderro Artz / Vaporsoft.