IDebug is experimental. Prefer enabling only in development.
Samples

Samples

Runnable demos in this monorepo (fixed ports for automation).

SamplePathPortSDKOpen
Expresssamples/express-api3001@idebug/nodehttp://localhost:3001/\_\_idebug
NestJSsamples/nest-api3002@idebug/nesthttp://localhost:3002/\_\_idebug
Databasesamples/db-api3003@idebug/node + @idebug/dbhttp://localhost:3003/\_\_idebug
Reactsamples/react-app5173@idebug/reactOverlay in-page

Run

pnpm install
pnpm build:packages
 
pnpm --filter sample-express-api start   # or: dev (tsx watch)
pnpm --filter sample-nest-api start
pnpm --filter sample-db-api start        # Drizzle + Knex call tree
pnpm --filter sample-react-app dev

Each sample folder has a README. The root monorepo README documents the full layout, CLI, and package map.

Demo routes (Express & Nest)

RoutePurpose
GET /healthSuccess
GET /calc/add?a=1&b=2Logged module / @Loggable success
GET /calc/divide?a=1&b=0Error path

Database sample (sample-db-api)

In-memory SQLite. Wrap clients with instrumentDrizzle / instrumentKnex, wrap services with logModule, then inspect Call tree at /__idebug.

RoutePurpose
GET /usersController → service → Drizzle SELECT
GET /users/1One request, two ORMs (Drizzle user/posts + Knex orders)
POST /usersInsert; password redacted on the dbQuery
GET /ordersKnex-only branch
GET /statsConcurrent Drizzle + Knex + raw traceQuery
GET /demo/n-plus-oneN+1: one user list + one orders query per user
GET /demo/slowFunction time vs query time
GET /demo/errorFailed SQL on the same tree

See @idebug/db and Database queries.

React sample

Buttons trigger fetch success, XHR success, and fetch failure. Open the floating ID control to inspect events.

Each sample folder has its own README with details.