tailwindcss/integrations
Philipp Spiess 719a5351c1
Fix Nuxt integration (#14319)
We noticed that Nuxt projects were not working with the tailwindcss
project. The issue was traced down to the fact that Nuxt starts multiple
Vite dev servers and calling the experimental `waitForRequestsIdle()` on
one of the test servers would never resolve.

This was fixed upstream and is part of the latest Vite/Nuxt release:
https://github.com/vitejs/vite/issues/17980.

We still need to handle the fact that Vite can spawn multiple dev
servers. This is necessary because when we invalidate all roots, we need
to find that module inside all of the spawned servers. If we only look
at the _last server_ (what we have done before), we would not find the
module and thus could not invalidate it.
2024-09-04 10:53:15 -04:00
..
cli Allow @plugin and @config to point to TS files (#14317) 2024-09-03 18:35:39 +02:00
postcss Ensure content globs defined in @config files are relative to that file (#14314) 2024-09-03 16:54:08 +02:00
vite Fix Nuxt integration (#14319) 2024-09-04 10:53:15 -04:00
package.json Add integration test setup and tests for the Vite integration (#14089) 2024-08-02 11:50:49 +02:00
utils.ts Rework Vite plugin to support lightningcss pre processor and fast rebuilds (#14269) 2024-09-04 10:09:24 +02:00