create-mf-app
create-mf-app copied to clipboard
Support for Tailwind CSS v3 ?
Do you plan to add the possibility to use Tailwind v3? I tried to manually update the settings (package.json, tailwind.config.js), but the classes of remote modules do not seem to be interpreted... It only works locally to each module.
Thanks for the awesome work!
Can you post up a PR that works-ish? And then I'll see if I can take it from there?
OK, I'll try.
Hello Jack, Done !
Best regards, Antoine
Le ven. 7 janv. 2022 à 17:08, Jack Herrington @.***> a écrit :
Can you post up a PR that works-ish? And then I'll see if I can take it from there?
— Reply to this email directly, view it on GitHub https://github.com/jherr/create-mf-app/issues/24#issuecomment-1007530492, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMWVNTKQSSEGXA7WHFJYAUTUU4FWFANCNFSM5LPBPQZA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
i found this https://github.com/jrandeniya/federated-types-sample
Any update?
IMHO Tailwind 3 is not an ideal match for Module Federation, at least without using a CSS in JS converter like twin macro. The issue is the optimization in Tailwind 3 that aggressively removes any unused classes. That's great for packaged apps. But the point of Module Federation is that part of the code is brought in at runtime. Which means that the optimizer won't know what classes are in that runtime code.