Skip to content

[Meta] DevTools suite — one product from visualizer, time-travel, tracing, profiling #445

Description

@pathosDev

Coordination umbrella — no new feature scope of its own; it makes five existing tickets ship as one product instead of five bolt-ons.

Rationale

Erlang's observer is a big part of why the BEAM feels magical: you can see the system. We have five separate tickets pointing at the same outcome — #204 (live cluster visualizer), #217 (dev-mode tracing visualizer), #218 (per-actor explain-plan), #201 (time-travel debugger over the journal), #226 (flame-graph profiler). Built independently they would each invent their own event tap and UI shell.

Scope (architecture clamp)

import { DevTools } from 'actor-ts/devtools';
DevTools.attach(system, { port: 9333 });
// http://localhost:9333 — live actor tree, message flow, mailbox depths; later time-travel (#201)

Documentation

DevTools docs chapter (EN + DE) grows with each panel; CHANGELOG per landed panel.

Acceptance (umbrella)

  • Shared tap protocol documented + versioned before the first panel merges; each panel issue references and reuses it; "./devtools" subpath export.

Relates

Tracks: #204, #217, #218, #201, #226. Feeds on #196 (mailbox metrics), #200 (simulation). Dependency policy #419. Improvement program M6.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions