Philipp Spiess 74ccde4672 Upgrade lightningcss to 1.29.2 in Standalone (#17169) ... Closes #17162 Closes #17163 Closes #17164 Closes #17165 Closes #17166 Closes #17167 Noticed that there was a second place pulling in the lightningcss version numbers that wasn't covered by the previous upgrade PR. Thankfully the APIs of the node bindings are still compatible. To avoid this mistake in the future I also exported these sub-packages as a workspace dependency so all the version strings appear right next to each other.		2025-03-13 11:18:06 +01:00
..
@tailwindcss-browser	Prepare release 4.0.13 (#17132)	2025-03-11 17:58:53 +01:00
@tailwindcss-cli	Prepare release 4.0.13 (#17132)	2025-03-11 17:58:53 +01:00
@tailwindcss-node	Prepare release 4.0.13 (#17132)	2025-03-11 17:58:53 +01:00
@tailwindcss-postcss	Prepare release 4.0.13 (#17132)	2025-03-11 17:58:53 +01:00
@tailwindcss-standalone	Upgrade lightningcss to 1.29.2 in Standalone (#17169)	2025-03-13 11:18:06 +01:00
@tailwindcss-upgrade	Prepare release 4.0.13 (#17132)	2025-03-11 17:58:53 +01:00
@tailwindcss-vite	Prepare release 4.0.13 (#17132)	2025-03-11 17:58:53 +01:00
internal-example-plugin	Prefix internal modules with internal-* (#14074)	2024-07-29 10:58:07 -04:00
tailwindcss	Add @source inline(…) (#17147)	2025-03-12 13:55:33 +00:00
tsconfig.base.json	Improve debug logs (#15303)	2024-12-11 15:27:20 +01:00