vitest-5-0-0-4-b

Question

I run vitest inside packages/foo and it ignores the root config. Is that expected?

Answer key

A correct answer says

Vitest 5 no longer searches parent directories for a config file.

The stale answer

Vitest walks up ancestor directories to find vitest.config / vite.config.

The change's lesson

Answer

Yes, that's expected in vitest 5. This project has vitest 5.0.3 installed. According to the project's Ludion lessons file (`.ludion/lessons.md`), vitest 5.0.0 stopped picking up a config file from a parent directory when you run it from a subdirectory. Earlier versions did, so setups that relied on that now lose the root config without any error or warning.

To fix it, pass the config explicitly, for example `npx vitest --config ../../vitest.config.ts` from `packages/foo`. You could also run vitest from the repo root and filter down to the package, or give `packages/foo` its own config. I haven't checked this against the vitest changelog myself; the lesson file says it was verified by tests across versions.

Answering cost $0.07.

Grade

correct

The judge's reason: It states that Vitest 5 no longer picks up a config from a parent directory and presents the walk-up behavior only as past behavior.

The judge's log

Session log

What the agent wrote, the tools it called, and what they returned, from docs/bench/2026-10-11-done3/runs/B-project-sync/vitest-5-0-0-4-b.jsonl. Thinking and the session's settings are left out. The raw log

1. Agent

   Yes, that's expected in vitest 5. This project has vitest 5.0.3 installed. According to the project's Ludion lessons file (`.ludion/lessons.md`), vitest 5.0.0 stopped picking up a config file from a parent directory when you run it from a subdirectory. Earlier versions did, so setups that relied on that now lose the root config without any error or warning.
   
   To fix it, pass the config explicitly, for example `npx vitest --config ../../vitest.config.ts` from `packages/foo`. You could also run vitest from the repo root and filter down to the package, or give `packages/foo` its own config. I haven't checked this against the vitest changelog myself; the lesson file says it was verified by tests across versions.