tailwindcss/packages
Adam Wathan 6d0371afb1
Evaluate theme functions in plugins (#14326)
This PR fixes a bug where CSS `theme()` functions were not evaluated
when present in rules added by plugins, using either `@plugin` or
registering a plugin in a JS config file.

For example, prior to this PR the `theme()` functions in this plugin
would make it into the final CSS without being evaluated:

```js
// ./my-plugin.js
export default plugin(({ addBase }) => {
  addBase({
    '.my-rule': {
      background: 'theme(colors.primary)',
      color: 'theme(colors.secondary)',
    },
  })
})
```

---------

Co-authored-by: Adam Wathan <4323180+adamwathan@users.noreply.github.com>
2024-09-04 11:49:01 -04:00
..
@tailwindcss-cli Ensure content globs defined in @config files are relative to that file (#14314) 2024-09-03 16:54:08 +02:00
@tailwindcss-node Allow @plugin and @config to point to TS files (#14317) 2024-09-03 18:35:39 +02:00
@tailwindcss-postcss Ensure content globs defined in @config files are relative to that file (#14314) 2024-09-03 16:54:08 +02:00
@tailwindcss-standalone Prepare v4.0.0-alpha.21 (#14313) 2024-09-02 15:43:28 -04:00
@tailwindcss-vite Fix Nuxt integration (#14319) 2024-09-04 10:53:15 -04:00
internal-example-plugin Prefix internal modules with internal-* (#14074) 2024-07-29 10:58:07 -04:00
internal-postcss-fix-relative-paths Support loading config files via @config (#14239) 2024-09-02 18:03:16 +02:00
tailwindcss Evaluate theme functions in plugins (#14326) 2024-09-04 11:49:01 -04:00
tsconfig.base.json introduce v4 codebase 2024-03-05 14:29:15 +01:00