vitest-5-0-0-14-b
Claude Code's read-only tools, web search on, ludion sync on
Question
Do I need extends: true for each inline project to pick up my root Vitest settings?
Answer key
- A correct answer says
- Inline projects in `test.projects` inherit the root config by default.
- The stale answer
- Inline projects do not inherit the root config unless you set `extends: true`.
Answer
No. On the vitest 5.0.3 this project installs, you don't need `extends: true`. Inline project configurations inherit options from the root-level config by default, so adding it to each project changes nothing.
That's different from Vitest 3.x/4.x, where inline projects did not inherit root settings unless you set `extends: true`. Config written for those versions still works on 5.x, and the flag is now just redundant. If you want a project to *not* inherit root settings, you'd now opt out explicitly, presumably with `extends: false`.
I'm getting the 5.0 default change from this project's `.ludion/lessons.md` note, which says it was test-verified. I haven't checked it against the installed vitest source.Grade
correct
The judge's reason: It states inline projects inherit the root config by default in Vitest 5, and mentions the extends: true requirement only as past 3.x/4.x behavior.
Session log
Agent
No. On the vitest 5.0.3 this project installs, you don't need `extends: true`. Inline project configurations inherit options from the root-level config by default, so adding it to each project changes nothing. That's different from Vitest 3.x/4.x, where inline projects did not inherit root settings unless you set `extends: true`. Config written for those versions still works on 5.x, and the flag is now just redundant. If you want a project to *not* inherit root settings, you'd now opt out explicitly, presumably with `extends: false`. I'm getting the 5.0 default change from this project's `.ludion/lessons.md` note, which says it was test-verified. I haven't checked it against the installed vitest source.