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

pool/runners

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

Default pool runners in Vitest

Vitest runs tests in a pool. The default pool runners are: threads (runs tests using node:worker_threads with isolation provided by a new worker context), forks (runs tests using node:child_process with isolation provided by child_process.fork), vmThreads (runs tests using node:worker_threads with isolation provided by vm module instead of a new worker context), browser (runs tests using browser providers), and typescript (runs typechecking on tests).

Default pool is forks

By default Vitest runs tests in pool: 'forks'. While forks pool is better for compatibility issues (hanging process and segfaults), it may be slightly slower than pool: 'threads' in larger projects.

Switch pool to threads with CLI or config

To improve test run time by switching pool option: use vitest --pool=threads on CLI, or set test.pool property to 'threads' in vitest.config.js.

Give your agent this brain