tailwindcss

mirror of https://github.com/tailwindlabs/tailwindcss.git synced 2025-12-08 21:36:08 +00:00

History

Fix resolving colors via theme(…) in compat mode with nested objects (#19097 )

This PR fixes an issue when loading (nested) colors from a config file
and later referencing it via the `theme(…)` function in CSS.

Given a config like this:

```js
module.exports = {
  theme: {
    colors: {
      foo: 'var(--foo-foo)',
      'foo-bar': 'var(--foo-foo-bar)',
    },
  },
}
```

We internally map this into the design system. The issue here is that
the `foo` and `foo-bar` are overlapping and it behaves more like this:

```js
{
  foo: {
    DEFAULT: 'var(--foo-foo)',
    bar: 'var(--foo-foo-bar)'
  },
}
```

So while we can easily resolve `colors.foo-bar`, the `colors.foo` would
result in the object with a `DEFAULT` key. This PR solves that by using
the `DEFAULT` key if we end up with an object that has it.

If you end up resolving an object (`theme(colors)`) then the behavior is
unchanged.


## Test plan

1. Added a test based on the config in the issue (which failed before
this fix).
2. Also simplified the test case after identifying the problem (with the
`DEFAULT` key).

Fixes: #19091

2025-10-09 17:10:32 +00:00

src

Fix resolving colors via theme(…) in compat mode with nested objects (#19097 )

2025-10-09 17:10:32 +00:00

package.json

Update globby 14.1.0 → 15.0.0 (major) (#19056 )

2025-10-06 11:14:31 +02:00

README.md

update READMEs

2025-07-02 22:49:47 +02:00

tsconfig.json

Internal refactor, introduce AtRule (#14802 )