Generally this means adding Tailwind as a plugin in your file: module. 4 Process your CSS with Tailwind Using Tailwind with PostCSSįor most projects, you'll want to add Tailwind as a PostCSS plugin in your build chain. Learn more about configuring Tailwind in the configuration documentation. You can optionally include the -p flag to generate a basic file at the same time: npx tailwindcss init -p This will create a minimal file at the root of your project: // If you'd like to customize your Tailwind installation, you can generate a config file for your project using the Tailwind CLI utility included when you install the tailwindcss npm package: npx tailwindcss init If you're using postcss-import (or a tool that uses it under the hood, such as Webpacker for Rails), use our imports instead of the directive to avoid issues when importing any of your own additional files: "tailwindcss/base" "tailwindcss/components" "tailwindcss/utilities" 3 Create your Tailwind config file (optional) Tailwind will swap these directives out at build time with all of its generated CSS. Use the directive to inject Tailwind's base, components, and utilities styles into your CSS: base components utilities # Using npm npm install Using Yarn yarn add 2 Add Tailwind to your CSS Platypus - A great program by Sveinbjorn Thordarson that encapsulates unpkg-script very nicely.For most projects (and to take advantage of Tailwind's customization features), you'll want to install Tailwind via npm.Old release (PowerPC only.if you just absolutely need the outdated and ugly text-only interface): unpkg-1.61.zip. more file selection dialogs if unpkg can't save the file in the chosen location. file selection dialogs if no package is dragged onto unpkg's icon.completely new interface: no more text output, but pretty Cocoa dialogs and progress bars.make explicit the fact that this is released under the GNU GPL.ripped out CocoaDialog, upgraded to a WebKit-based interface.also now extracts 10.5-style packages (nested ones, too, and in 10.4 as well!).now works with multiple packages at once.we skipped 3.0 because it's so much better and different! lots of behind-the-scenes changes and fixes.Rebuild as a 64 bit binary for macOS Catalina compatibility.Native Apple Silicon support: rebuild w/ arm64 and x86_64 binaries.Ported from Python 2 to 3 due to the former's deprecation in macOS 12.3.good package detection (unpkg will not try to unpack something that's not a package, and easily handles malformed packages).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |