tailwindcss/integrations
Philipp Spiess d3846a4570
Update test to retry assertion on empty file and don't include forward-slash in the assertion (#17821)
To fix the CI issues we have, it turns out there are two issues:

1. The file-read was not retried, making it possible for all platforms
(but mostly Windows because it's the slowest) to sometimes not have the
file created yet before making the assertion.
2. A forward-slash in the assertion message path would always be a
backslash when run on Windows, thus the Windows test would never pass.

## Test plan

 - [ci-all] and have the test pass two times.
2025-04-29 18:16:58 +02:00
..
cli Polyfill: Fall back to first color value when color-mix(…) contains unresolvable var(…) (#17513) 2025-04-03 15:12:34 +00:00
oxide Add experimental @tailwindcss/oxide-wasm32-wasi (#17558) 2025-04-11 17:19:55 +02:00
postcss Update test to retry assertion on empty file and don't include forward-slash in the assertion (#17821) 2025-04-29 18:16:58 +02:00
upgrade Ensure @tailwindcss/upgrade runs on Tailwind CSS v4 projects and is idempotent (#17717) 2025-04-22 11:10:46 -04:00
vite Vite: Don't register the current CSS file as a dependency on itself (#17533) 2025-04-03 18:50:16 +02:00
webpack Fix slow incremental builds (especially on Windows) (#17511) 2025-04-03 17:13:15 +02:00
package.json Update fast-glob 3.3.2 → 3.3.3 (patch) (#15607) 2025-01-13 11:11:35 +01:00
utils.ts Temporarily disable broken Windows test 2025-04-28 10:53:46 +02:00
vitest.config.ts Improve integration tests (stability + performance) (#15125) 2024-12-12 13:48:56 +01:00