Skip to content

docs: note browser condition earlier #14096

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 1, 2024
Merged

docs: note browser condition earlier #14096

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
67cccac
docs: note browser condition earlier
dummdidumm Nov 1, 2024
832e561
Update documentation/docs/07-misc/02-testing.md
Rich-Harris Nov 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion documentation/docs/07-misc/02-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,18 @@ Then adjust your `vite.config.js`:
/// file: vite.config.js
import { defineConfig } from +++'vitest/config'+++;

export default defineConfig({ /* ... */ })
export default defineConfig({
// ...
// Tell Vitest to use the `browser` entry points in `package.json` files, even though it's running in Node
resolve: process.env.VITEST
? {
conditions: ['browser']
}
: undefined
```

> [!NOTE] If loading the browser version of all your packages is undesirable, because (for example) you also test backend libraries, [you may need to resort to an alias configuration](https://github.com/testing-library/svelte-testing-library/issues/222#issuecomment-1909993331)

You can now write unit tests for code inside your `.js/.ts` files:

```js
Expand Down