Skip to content

Commit a40a4d5

Browse files
committed
fixup: typos and tweaks
1 parent 9512d54 commit a40a4d5

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

docs/svelte-testing-library/faq.mdx

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,9 @@ import {defineConfig} from 'vite'
3030
export default defineConfig(({mode}) => ({
3131
plugins: [svelte()],
3232
resolve: {
33-
// the default would be [ 'svelte', 'node' ]
34-
// as set by vite-plugin-svelte and vitest
33+
// The default would be [ 'svelte', 'node' ]
34+
// as set by vite-plugin-svelte and vitest.
35+
// This sets [ 'browser', 'svelte', 'node' ]
3536
conditions: mode === 'test' ? ['browser'] : [],
3637
},
3738
test: {
@@ -73,10 +74,11 @@ test('upload file', async () => {
7374

7475
## Why aren't [transition events][] running?
7576

76-
The [jsdom][] `requestAnimationFrame` implementation can be unreliable in
77-
Vitest. To work around it, you can try a few things:
77+
The [jsdom][] implementation of `requestAnimationFrame` can be unreliable in
78+
Vitest. To work around it, you can:
7879

79-
- Switch [happy-dom][], if you are able, which does not exhibit the same issues
80+
- Switch to [happy-dom][], if you are able, which does not exhibit the same
81+
issues
8082
- Replace the implementation of `requestAnimationFrame`
8183

8284
```js

0 commit comments

Comments
 (0)