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

Vitest · Guide · all subjects

browser/debugging

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

Debug browser tests with Node Inspector

Run vitest --inspect-brk --browser --no-file-parallelism to debug browser tests using Node Inspector and Chrome DevTools.

Debug browser tests with VS Code extension

The official VS Code extension for Vitest provides the simplest way to debug browser tests.

Debug browser tests with --inspect-brk flag

Use --inspect-brk or --inspect flag in CLI or set inspectBrk configuration to debug browser tests. Combine with --browser and --no-file-parallelism flags.

Default debugging port for browser mode

Vitest uses port 9229 as the default debugging port for browser mode. Override it by passing a value to --inspect-brk, for example: vitest --inspect-brk=127.0.0.1:3000 --browser --no-file-parallelism.

Give your agent this brain