tailwindcss/packages
Robin Malfait 78b4864d30 always emit , ) instead of ,) for fallback values in CSS variables
This will bring the development version and production version closer
together. It also means that the development version works in older
supported browsers like  Chrome v112 where the space is required (even
though the spec allows both)

There are no changes in tests just becaues we already run each test
through Lightning CSS which normalizes these values:

Input:
```css
var(--tw-blur,)
var(--tw-blur, )
```

Lightning CSS output:
```css
var(--tw-blur, )
var(--tw-blur, )
```
2026-07-31 14:53:47 +02:00
..
@tailwindcss-browser 4.3.3 (#20334) 2026-07-16 07:21:50 -04:00
@tailwindcss-cli 4.3.3 (#20334) 2026-07-16 07:21:50 -04:00
@tailwindcss-node 4.3.3 (#20334) 2026-07-16 07:21:50 -04:00
@tailwindcss-postcss 4.3.3 (#20334) 2026-07-16 07:21:50 -04:00
@tailwindcss-standalone 4.3.3 (#20334) 2026-07-16 07:21:50 -04:00
@tailwindcss-upgrade 4.3.3 (#20334) 2026-07-16 07:21:50 -04:00
@tailwindcss-vite 4.3.3 (#20334) 2026-07-16 07:21:50 -04:00
@tailwindcss-webpack 4.3.3 (#20334) 2026-07-16 07:21:50 -04:00
internal-example-plugin Prefix internal modules with internal-* (#14074) 2024-07-29 10:58:07 -04:00
tailwindcss always emit , ) instead of ,) for fallback values in CSS variables 2026-07-31 14:53:47 +02:00
tsconfig.base.json Improve debug logs (#15303) 2024-12-11 15:27:20 +01:00