philipp-spiess 816e7307de Escape JS theme configuration keys (#14739) ...

This PR fixes two issues related to how we tread JS theme keys in combination with CSS theme values:

1. When applying JS theme keys to our `Theme` class, we need to ensure they are escaped in the same way as reading CSS theme keys from CSS are.
2. When JS plugins use the `theme()` function to read a namespace that has values contributed to from the CSS theme and the JS theme, we need to ensure that the resulting set contains only unescaped theme keys.

For specific examples, please take a look at the test cases.

2024-10-22 16:56:16 +00:00

..

@tailwindcss-cli

Ensure changes to the input CSS file result in a full rebuild (#14744)

2024-10-21 20:29:33 +00:00

@tailwindcss-node

Prepare v4.0.0-alpha.28 release (#14709)

2024-10-17 17:03:28 -04:00

@tailwindcss-postcss

Prepare preflight for border compatibility (#14745)

2024-10-22 16:18:13 +00:00

@tailwindcss-standalone

Update @types/bun 1.1.10 → 1.1.11 (patch) (#14727)

2024-10-19 15:18:39 +02:00

@tailwindcss-upgrade

Upgrade: Migrate max-w-screen-* candidates (#14754)

2024-10-22 16:40:42 +00:00

@tailwindcss-vite

Vite: Fix issues when loading files via static asset queries (#14716)

2024-10-22 16:03:07 +00:00

internal-example-plugin

Prefix internal modules with internal-* (#14074)

2024-07-29 10:58:07 -04:00

tailwindcss

Escape JS theme configuration keys (#14739)

2024-10-22 16:56:16 +00:00

tsconfig.base.json

introduce v4 codebase

2024-03-05 14:29:15 +01:00