Update dependency @tailwindcss/vite to v4.2.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@tailwindcss/vite (source)	4.2.2 → 4.2.4

---

Release Notes

tailwindlabs/tailwindcss (@​tailwindcss/vite)

v4.2.4

Compare Source

Fixed

• Ensure imports in @import and @plugin still resolve correctly when using Vite aliases in @tailwindcss/vite (#​19947)

v4.2.3

Compare Source

Fixed

• Canonicalization: improve canonicalizations for tracking-* utilities by preferring non-negative utilities (e.g. -tracking-tighter → tracking-wider) (#​19827)
• Fix crash due to invalid characters in candidate (exceeding valid unicode code point range) (#​19829)
• Ensure query params in imports are considered unique resources when using @tailwindcss/webpack (#​19723)
• Canonicalization: collapse arbitrary values into shorthand utilities (e.g. px-[1.2rem] py-[1.2rem] → p-[1.2rem]) (#​19837)
• Canonicalization: collapse border-{t,b}-* into border-y-*, border-{l,r}-* into border-x-*, and border-{t,r,b,l}-* into border-* (#​19842)
• Canonicalization: collapse scroll-m{t,b}-* into scroll-my-*, scroll-m{l,r}-* into scroll-mx-*, and scroll-m{t,r,b,l}-* into scroll-m-* (#​19842)
• Canonicalization: collapse scroll-p{t,b}-* into scroll-py-*, scroll-p{l,r}-* into scroll-px-*, and scroll-p{t,r,b,l}-* into scroll-p-* (#​19842)
• Canonicalization: collapse overflow-{x,y}-* into overflow-* (#​19842)
• Canonicalization: collapse overscroll-{x,y}-* into overscroll-* (#​19842)
• Read from --placeholder-color instead of --background-color for placeholder-* utilities (#​19843)
• Upgrade: ensure files are not emptied out when killing the upgrade process while it's running (#​19846)
• Upgrade: use config.content when migrating from Tailwind CSS v3 to Tailwind CSS v4 (#​19846)
• Upgrade: never migrate files that are ignored by git (#​19846)
• Add .env and .env.* to default ignored content files (#​19846)
• Canonicalization: migrate overflow-ellipsis into text-ellipsis (#​19849)
• Canonicalization: migrate start-full → inset-s-full, start-auto → inset-s-auto, start-px → inset-s-px, and start-<number> → inset-s-<number> as well as negative versions (#​19849)
• Canonicalization: migrate end-full → inset-e-full, end-auto → inset-e-auto, end-px → inset-e-px, and end-<number> → inset-e-<number> as well as negative versions (#​19849)
• Canonicalization: move the - sign inside the arbitrary value -left-[9rem] → left-[-9rem] (#​19858)
• Canonicalization: move the - sign outside the arbitrary value ml-[calc(-1*var(--width))] → -ml-(--width) (#​19858)
• Improve performance when scanning JSONL / NDJSON files (#​19862)
• Support NODE_PATH environment variable in standalone CLI (#​19617)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[netlify]

❌ Deploy Preview for nifty-bardeen-5c7e53 failed.

Name	Link
🔨 Latest commit	adfb434
🔍 Latest deploy log	https://app.netlify.com/projects/nifty-bardeen-5c7e53/deploys/69fa3f48b951e200084d79ea

[andygrunwald]

Build failure analysis — Missing field tsconfigPaths on BindingViteResolvePluginConfig.resolveOptions

Root cause

Two upstream changes collided:

1. vite 8.0.10 (released 2026-04-23, vitejs/vite#22299) bumped its bundled rolldown to 1.0.0-rc.17. That release added a required tsconfigPaths field to BindingViteResolvePluginConfig.resolveOptions.
2. @tailwindcss/vite 4.2.3 (tailwindlabs/tailwindcss#19803) and 4.2.4 (tailwindlabs/tailwindcss#19947) introduced a customCssResolver / customJsResolver that calls Vite's resolver for @reference, @import and @plugin directives. That call path doesn't pass the new tsconfigPaths field, so rolldown rc.17 throws.

@tailwindcss/vite 4.2.2 doesn't take this code path → main builds fine. 4.2.4 always takes it for any CSS file with @reference / @plugin. We have several:

• src/pages/podcast-werbung.astro:57
• src/pages/index.astro:232
• src/pages/deutsche-tech-podcasts/index.astro:74
• src/components/PodcastEpisodeTranscript.astro:21
• src/styles/global.css:4 (@plugin '@tailwindcss/typography')

Why this hits us specifically

node_modules/ ends up with two vite trees:

Location	Version	Brought by	rolldown
node_modules/vite (root)	8.0.10	vitest@4.1.5	rc.17 (broken)
node_modules/astro/node_modules/vite	7.3.2	astro@6.1.5 (peer ^7.3.1)	older, fine

@tailwindcss/vite is hoisted at the root and resolves vite to the root copy → it pulls in vite 8.0.10's broken resolver bindings even though astro itself runs the build with the nested 7.3.2. The error trace confirms this — every frame is node_modules/vite/..., not node_modules/astro/node_modules/vite/....

The same vite 8.0.10 was confirmed as the trigger in vitejs/vite#22322 (closed; reporter believes the fix belongs upstream in tailwind/astro). Multiple other repos pinned past 4.2.4 as a workaround. There is no fixed @tailwindcss/vite release yet (latest is 4.2.4).

Options

1. Pin root vite to 8.0.9 (still ships rolldown rc.16 without the required field) by adding "vite": "8.0.9" to devDependencies. Compatible with vitest (peer ^6 || ^7 || ^8) and @tailwindcss/vite (peer ^5.2 || ^6 || ^7 || ^8); astro keeps its nested 7.3.2 untouched. Single-line, trivially revertible once upstream is fixed.
2. Hold this PR until @tailwindcss/vite 4.2.5+ (or a rolldown release with the binding fix) lands. No code change, but no ETA from upstream.
3. Add a renovate package rule to skip 4.2.3/4.2.4 explicitly until a fix exists.

Recommended: option 1 if we want to merge soon, option 2 if we prefer to wait for the upstream resolution.