The front door for the OCPP DebugKit ecosystem: the marketing site, the documentation, and the in-browser trace inspector — a zero-install tool that parses OCPP traces, detects failures, and generates reports entirely in your browser.
This is a Next.js app. The inspector is powered by the
published @ocpp-debugkit/toolkit
npm package — the site depends on the released library, not on a workspace build.
OCPP DebugKit is two independent products that share one trace format:
| Project | Language | Surface | Role |
|---|---|---|---|
toolkit |
TypeScript | npm library · CLI · web inspector | Parse, analyze, and report OCPP traces anywhere |
studio |
Zig | native desktop app | Live capture, native performance, OS integration |
This repository is the shared website for both.
Requires Node.js 20+ and pnpm 10+.
pnpm install # install dependencies (pulls @ocpp-debugkit/toolkit from npm)
pnpm dev # start the dev server at http://localhost:3000
pnpm build # production build
pnpm typecheck # TypeScript type checking
pnpm lint # ESLint
pnpm test:e2e # Playwright end-to-end testssrc/app/
├── page.tsx # Landing page
├── layout.tsx # Root layout
├── inspector/ # In-browser trace inspector (client-side)
└── docs/ # Documentation pages
tests/ # Playwright end-to-end specs
The site deploys to Vercel. Pushes to main publish to
production; pull requests get preview deployments.
See CONTRIBUTING.md and our Code of Conduct. Contributors using AI coding agents should point them at AGENTS.md.
Issues about the library belong in the
toolkit repo, and issues about the
native app belong in studio.
Apache 2.0 © OCPP DebugKit Contributors