Astro not working with latest TailwindCSS

[qtzar]

Astro Info

Astro                    v5.10.2
Node                     v24.3.0
System                   macOS (arm64)
Package Manager          npm
Output                   static
Adapter                  none
Integrations             @astrojs/markdoc
                         astro-icon
                         pagefind
                         relative-links
                         astro-expressive-code
                         @astrojs/mdx

If this issue only occurs in one browser, which browser is a problem?

N/A

Describe the Bug

When running Astro with the latest 4.1.11 version of TailwindCSS and @tailwindcss/vite dependancies the following error is reported during build. Reverting back to versions 4.1.10 resolves the issue. I suspect it is due to tailwind adding support for Vite 7.

astro.config.mjs:108:13 - error ts(2322): Type 'Plugin$1[]' is not assignable to type 'PluginOption'.
Type 'Plugin$1[]' is not assignable to type 'PluginOption[]'.

108 plugins: [tailwindcss()],
~~~~~~~~~~~~~

Note, I cannot get StackBlitz to install any dependancies due to an internal npm error. Trying to resolve.

What's the expected result?

Expect build to process normally and not exit with an error

Link to Minimal Reproducible Example

https://stackblitz.com/~/github.com/qtzar/github-pbzfummy

Participation

• I am willing to submit a pull request for this issue.

[qtzar]

Having issues duplicating error on StackBlitz, however viewing the astro.config.mjs file shows the tailwindcss plugin config red underlines with the same error.

[oceangravity]

Same here with Vite 7. I fixed it with Vite 6.3.5

[fshowalter]

This is because Tailwind will pull in vite 7 while astro still uses 6, creating a type mismatch. #14025 should resolve it when merged. As @oceangravity pointed out, using an "overrides" to pin vite to 6.3.5 will fix it until Astro updates.

[florian-lefebvre]

Vite plugin types are known to be fragile, it can even break between minors. Vite 7 requires a major so it will be part of Astro 6, later this year (withastro/roadmap#1174). In the meantime, you can add a // @ts-expect-error comment safely

[matthewp]

Fixed by #14445