4079059420
This PR fixes an issue where imports above Tailwind directives didn't get a `layer(…)` argument. Given this CSS: ```css @import "./typography.css"; @tailwind base; @tailwind components; @tailwind utilities; ``` It was migrated to: ```css @import "./typography.css"; @import "tailwindcss"; ``` But to ensure that the typography styles end up in the correct location, it requires the `layer(…)` argument. This PR now migrates the input to: ```css @import "./typography.css" layer(base); @import "tailwindcss"; ``` Test plan: --- Added an integration test where an import receives the `layer(…)`, but an import that eventually contains `@utility` does not receive the `layer(…)` argument. This is necessary otherwise the `@utility` will be nested when we are processing the inlined CSS. Running this on the Commit template, we do have a proper `layer(…)` <img width="585" alt="image" src="https://github.com/user-attachments/assets/538055e6-a9ac-490d-981f-41065a6b59f9"> |
||
|---|---|---|
| .. | ||
| @tailwindcss-cli | ||
| @tailwindcss-node | ||
| @tailwindcss-postcss | ||
| @tailwindcss-standalone | ||
| @tailwindcss-upgrade | ||
| @tailwindcss-vite | ||
| internal-example-plugin | ||
| tailwindcss | ||
| tsconfig.base.json | ||