tailwindcss/integrations
Robin Malfait 479b725cd3
Bump Vitest to v4 (#19216)
This PR bumps Vitest from v2 to v4. As far as I know we don't use any
Vitest specific features in our tests, but had to upgrade the
`vitest.workspace.ts` file to a `vitest.config.ts` file instead.

The only features we use are the typical `describe`, `it`, `test`, and
`expect` functions.

The only other part we use is `vi.spyOn` and `vi.fn` but those didn't
change in API either.

The test shards were removed to prevent errors. Not all suites have
enough files / tests to be broken up into 3 parts so Vitest now errors
when that happens.

### Test plan

1. All tests should pass in CI.
2. All integration tests should pass in CI.

---------

Co-authored-by: Jordan Pittman <jordan@cryptica.me>
2025-11-20 18:16:20 -05:00
..
cli Include filename and line numbers in CSS parse errors (#19282) 2025-11-10 13:29:23 -05:00
oxide Remove Oxide postinstall script (#19149) 2025-10-19 10:50:21 +02:00
postcss Fix validation of source(…) paths (#19274) 2025-11-06 16:24:17 -05:00
upgrade Bump Vitest to v4 (#19216) 2025-11-20 18:16:20 -05:00
vite Support Vite Environment API (#18970) 2025-11-18 12:38:57 -05:00
webpack Fix slow incremental builds (especially on Windows) (#17511) 2025-04-03 17:13:15 +02:00
package.json Update dedent 1.6.0 → 1.7.0 (minor) (#19010) 2025-09-26 14:42:26 -04:00
utils.ts Bump Vitest to v4 (#19216) 2025-11-20 18:16:20 -05:00
vitest.config.ts Improve integration tests (stability + performance) (#15125) 2024-12-12 13:48:56 +01:00