tailwindcss

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

History

content rules from the JS config that are also covered by the automatic source detection should not be migrated to CSS (#14714 )

This PR changes the migration of `content` rules in the JS config to CSS codemods.

When a `content` rule is processed which matches files that are _also matched by the automatic content discovery in v4_, we do not need to emit CSS for that rule. 

Take, for example this v3 configuration file:

```ts
import { type Config } from 'tailwindcss'

module.exports = {
  content: [
    './src/**/*.{html,js}', 
    './node_modules/my-external-lib/**/*.{html}'
  ],
} satisfies Config
```

Provided the base directories match up, the first rule will also be covered by the automatic content discovery in v4 and thus we only need to convert the second rule to CSS:

```css
@import "tailwindcss";
@source '../node_modules/my-external-lib/**/*.{html}';
```

2024-10-18 15:48:56 +02:00

src

content rules from the JS config that are also covered by the automatic source detection should not be migrated to CSS (#14714 )

2024-10-18 15:48:56 +02:00

package.json

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

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

README.md

Add initial codemod tooling (#14434 )

2024-09-18 16:45:43 +02:00

tsconfig.json

Detect and migrate static plugin usages (#14648 )