tailwindcss/packages
Adam Wathan a022905279
Ensure --spacing-* variables take precedence over --container-* variables (#15180)
Fixes #15146.

This PR updates the `w-*`, `max-w-*`, `min-w-*`, and `basis-*` utilities
to make sure that `--spacing-*` values are preferred over
`--container-*` values when there is a conflict.


Given this theme configuration:

```css
@theme {
 --spacing-sm: 8px;
 --container-sm: 256px;
}
```

…utilities like `max-w-sm` will use `8px` instead of `256px` after this
change.

Users can still be explicit about the value they want to use if they've
introduced a naming collision like this by using our variable shorthand
like `max-w-(--container-sm)`.

---------

Co-authored-by: Adam Wathan <4323180+adamwathan@users.noreply.github.com>
2024-11-26 09:45:16 -05:00
..
@tailwindcss-cli Set browser targets for iOS Safari, Firefox, and Chrome (#15166) 2024-11-26 11:22:12 +00:00
@tailwindcss-node Prepare v4.0.0-beta.2 release (#15104) 2024-11-22 11:17:21 -05:00
@tailwindcss-postcss Set browser targets for iOS Safari, Firefox, and Chrome (#15166) 2024-11-26 11:22:12 +00:00
@tailwindcss-standalone Prepare v4.0.0-beta.2 release (#15104) 2024-11-22 11:17:21 -05:00
@tailwindcss-upgrade Update tree-sitter 0.22.0 → 0.22.1 (minor) (#15130) 2024-11-26 14:06:25 +01:00
@tailwindcss-vite Set browser targets for iOS Safari, Firefox, and Chrome (#15166) 2024-11-26 11:22:12 +00:00
internal-example-plugin Prefix internal modules with internal-* (#14074) 2024-07-29 10:58:07 -04:00
tailwindcss Ensure --spacing-* variables take precedence over --container-* variables (#15180) 2024-11-26 09:45:16 -05:00
tsconfig.base.json introduce v4 codebase 2024-03-05 14:29:15 +01:00