Philipp Spiess 1238d07ca2 Reference imports should not generate utilities (#15307) ... We noticed an issue where the new `@import "…" reference` syntax was not throwing away `@tailwind` declarations, effectively causing you to create utility classes whenever you used this feature. This is especially noticed in setups with very strict compilers like Svelte. ## Test Plan ### Before <img width="1142" alt="Screenshot 2024-12-05 at 11 56 00" src="https://github.com/user-attachments/assets/546f0eb3-4401-48c9-9268-76992e899226"> ### After <img width="2560" alt="Screenshot 2024-12-05 at 12 27 30" src="https://github.com/user-attachments/assets/16732000-e02c-49bc-ac6f-91da0cfcc7e8">		2024-12-05 16:18:06 +01:00
..
@tailwindcss-cli	Prepare v4.0.0-beta.5 (#15285)	2024-12-04 16:28:16 +01:00
@tailwindcss-node	Prepare v4.0.0-beta.5 (#15285)	2024-12-04 16:28:16 +01:00
@tailwindcss-postcss	Prepare v4.0.0-beta.5 (#15285)	2024-12-04 16:28:16 +01:00
@tailwindcss-standalone	Prepare v4.0.0-beta.5 (#15285)	2024-12-04 16:28:16 +01:00
@tailwindcss-upgrade	Prepare v4.0.0-beta.5 (#15285)	2024-12-04 16:28:16 +01:00
@tailwindcss-vite	Prepare v4.0.0-beta.5 (#15285)	2024-12-04 16:28:16 +01:00
internal-example-plugin	Prefix internal modules with internal-* (#14074)	2024-07-29 10:58:07 -04:00
tailwindcss	Reference imports should not generate utilities (#15307)	2024-12-05 16:18:06 +01:00
tsconfig.base.json	introduce v4 codebase	2024-03-05 14:29:15 +01:00