Entry points
@repobuddy/vitest has six entry points. Each has an import condition only; there is no CommonJS build.
| Import | Exports |
|---|---|
@repobuddy/vitest/config/node |
nodeTestPreset, buddyConfigDefaults, mergeConfig |
@repobuddy/vitest/config/browser |
browserTestPreset, buddyConfigDefaults, mergeConfig |
@repobuddy/vitest/config |
nodeTestPreset, browserTestPreset, buddyConfigDefaults, mergeConfig |
@repobuddy/vitest/setup/order |
Nothing. A setup file that adds expect.order. |
@repobuddy/vitest/setup/browser |
Nothing. The setup file browserTestPreset() adds. |
@repobuddy/vitest |
Re-exports @repobuddy/test: AssertOrder, InvalidOrder, installOrder, isRunningInTest, order, and the ExpectWithOrder and OrderApi types |
Which config entry to import
Section titled “Which config entry to import”@repobuddy/vitest/config/browserand@repobuddy/vitest/configimport@vitest/browser-playwrightwhen they load. Without that optional peer installed, the import fails.- In a Node.js-only project, import from
@repobuddy/vitest/config/node. It does not load@vitest/browser-playwright.
The preset option types (PresetOptions, NodePresetOptions) are not exported. Use
Parameters<typeof nodeTestPreset>[0] or Parameters<typeof browserTestPreset>[0]. Both presets return Vite’s
Plugin type.