I encourage you to come join the Meteor JS community and share some of your work.
Meteor has a mostly "magical" build tool that makes most developers not even ever realize it's happening, however, we're also seeing Svelte + Meteor apps being built and Svelte seems to take the Runtime approach as well. I'm developing a lot with Meteor, Vue, and Bootstrap personally, but I'm also actively working to contribute to both the Meteor and Vue open source projects. This seems pretty cool Nick ? I followed your comment on the Meteor + TailwindCSS post. It is possible to add a prefix to all RunCSS utilities by calling configure with a prefix option. And make sure that your RunCSS classes are added under an element with the 'app' id or whatever you specified. Importing Webscript import builders from ' ' import createDOMElement from ' ' // Importing RunCSS import processClasses from ' ' // Integrating RunCSS with Webscript function createElement ( type, props. Add a CSS reset or base CSS file, such as TailwindCSS's preflight, to your web application: CSS is only generated for class names that are actually used. The necessary CSS for each class name is generated one time as it is encountered. The tradeoff to using RunCSS is a small amount of Javascript execution to generate CSS at runtime. The primary difference between TailwindCSS and RunCSS is that TailwindCSS generates CSS at build time and RunCSS generates CSS at runtime. RunCSS is possible because it is a Javascript file that generates CSS at runtime. and responsive variants such as sm, lg etc work with all class names. By default all variants such as hover, active, visited, group-hover etc.
#Tailwindcss unpkg plus#
RunCSS defaults are the same as TailwindCSS defaults plus TailwindCSS's additional variants, plus more.
It has feature parity with TailwindCSS and beyond. RunCSS provides all the same CSS utility class names that we know and love from TailwindCSS. RunCSS is a runtime version of TailwindCSS. I don't want to use a huge bloated CSS file that is limited and can't be customized.I don't want to process my CSS with build tools.It is also not possible to customize the CDN file and some pseudo-class variants are missing. To pull in Tailwind for quick demos or just giving the framework a spin, grab the latest default configuration build via CDN. The TailwindCSS documentation dissuades people from using the CDN file in production with this: If you measure this file today like I did you find that it is 135kb compressed and 1,328kb raw.īut it isn't important. TailwindCSS documentation says this CDN file size is 27kb compressed and 348kb raw.