Robin Malfait 430836f651 Ensure layer(…) on @import is only removed when @utility is present (#14783) ... This PR fixes an issue where `layer(…)` next to imports were removed where they shouldn't have been removed. The issue exists if _any_ of the `@import` nodes in a file contains `@utility`, if that's the case then we removed the `layer(…)` next to _all_ `@import` nodes. Before we were checking if the current sheet contained `@utility` or in any of its children (sub-`@import` nodes). This fixes that by looping over the `@import` nodes in the current sheet, and looking for the `@utility` in the associated/imported file. This way we update each node individually. Test plan: --- Added a dedicated integration test to make sure all codemods together result in the correct result. Input: 96e8908378/integrations/upgrade/index.test.ts (L2076-L2108) Output: 96e8908378/integrations/upgrade/index.test.ts (L2116-L2126)		2024-10-24 14:33:10 -04:00
..
@tailwindcss-cli	Update picocolors 1.0.1 → 1.1.1 (minor) (#14771)	2024-10-24 11:25:50 +02:00
@tailwindcss-node	Resolve third-party plugins with exports in their package.json (#14775)	2024-10-24 11:34:19 -04:00
@tailwindcss-postcss	Prepare v4.0.0-alpha.29 release (#14761)	2024-10-23 15:30:26 +02:00
@tailwindcss-standalone	Prepare v4.0.0-alpha.29 release (#14761)	2024-10-23 15:30:26 +02:00
@tailwindcss-upgrade	Ensure layer(…) on @import is only removed when @utility is present (#14783)	2024-10-24 14:33:10 -04:00
@tailwindcss-vite	Prepare v4.0.0-alpha.29 release (#14761)	2024-10-23 15:30:26 +02:00
internal-example-plugin	Prefix internal modules with internal-* (#14074)	2024-07-29 10:58:07 -04:00
tailwindcss	Improve support for custom variants in group-*, peer-*, has-*, and not-* variants (#14743)	2024-10-24 13:27:27 -04:00
tsconfig.base.json	introduce v4 codebase	2024-03-05 14:29:15 +01:00