new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Deno · Reference · all subjects

vscode/debugging

5 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

VS Code debugger configuration for Deno

To debug a Deno project, go to the Run and Debug panel, click create a launch.json file, and select Deno from the available debugger options. The generated configuration will have type set to node, which is correct.

Debugging a dev server with VS Code

For projects that run a dev server through another tool (like Fresh with Vite), add a debug variant task to deno.json that runs the server with --inspect flag. Then create an attach configuration in .vscode/launch.json to connect VS Code to port 9229. Use --inspect-wait instead of --inspect if you need to debug code that runs during startup.

deno.json dev:debug task example

Example for debugging a Fresh app with Vite: ```json { "tasks": { "dev": "vite", "dev:debug": "deno run --inspect -A npm:vite" } } ``` --inspect starts the V8 inspector on 127.0.0.1:9229 without pausing.

.vscode/launch.json attach configuration example

Example attach configuration for debugging a dev server: ```json { "version": "0.2.0", "configurations": [ { "name": "Attach to dev server", "type": "node", "request": "attach", "port": 9229 } ] } ```

Unbound breakpoint in Vite

When debugging with Vite, a breakpoint in a route that hasn't been requested yet may show as "Unbound breakpoint" with a warning. This is expected behavior: the breakpoint binds once the route is first loaded, and it still pauses when that code runs.

Give your agent this brain