dev-debug-logslisted

Use when debugging an app through `fusebase dev start`, or when you need to inspect browser logs, proxied API traffic, frontend dev server output, or backend output captured by the local CLI. Explains where logs are written and which file to inspect for each symptom. This is for LOCAL DEVELOPMENT only - for deployed apps, use the remote-logs skill instead.
fusebase-dev/fusebase-flow · ★ 2 · Code & Development · score 75

Install: claude install-skill fusebase-dev/fusebase-flow

# Dev Debug Logs > **Important**: This skill is for **local development** only. For logs from deployed app backends, use the **remote-logs** skill with `fusebase remote-logs` command. When an app is run through: ```bash fusebase dev start FEATURE_PATH ``` the CLI creates a per-session log directory inside the selected app directory: ```text <app-dir>/logs/dev-<timestamp>/ ``` with these files: - `browser-logs.jsonl` - `access-logs.jsonl` - `backend-logs.jsonl` - `frontend-dev-server-logs.jsonl` Use this skill when debugging the local app runtime. These logs are local development artifacts only. ## Which Log File To Read ### `browser-logs.jsonl` Use for: - `console.log` / `console.error` output from the browser - uncaught browser errors - unhandled promise rejections - navigation/lifecycle events from the app page Important: - It only works when the app is opened through the CLI proxy started by `fusebase dev start` - The CLI injects a browser debug script into proxied HTML pages automatically - Records are JSON Lines; each line is one event Typical fields: - `timestamp` - `type` - `level` - `message` - `args` - `error` - `url` - `pathname` ### `backend-logs.jsonl` Use for: - backend stdout/stderr captured during `fusebase dev start` - runtime errors printed by an app backend - startup messages like port binding, env/config issues, and stack traces Typical fields: - `timestamp` - `appId` - `line` Important: - If the app defines a dedicated backend dev co