Rust-native Tailwind CSS v4.1-equivalent toolchain.
ironframe is a production-ready Rust OSS toolchain targeting high compatibility with Tailwind CSS v4.1 behavior and output. Separate scanner, generator, config, and CLI modules help teams benchmark, validate, and ship in a Node-free pipeline.
Production-ready CLI
scan, build, and watch support one-shot builds, watch mode, ignore globs, minified output, and compare-css validation during migration.
Tailwind-compatible pipeline
Supports @import "tailwindcss", @source include/exclude/inline patterns, @apply, split imports, and build-time functions such as --spacing() and --alpha().
Modular Rust architecture
Independent core, scanner, generator, and config components make profiling, compatibility checks, and incremental extension straightforward.
Set up and validate a CSS workflow
Start with cargo install or cargo run, then apply scan, build, and watch in stages. During migration, compare against your reference CSS and lock behavior with ironframe.toml.
Install
cargo install --path .
CLI Example
# 1) Run without installing
cargo run -- scan "src/**/*.{html,tsx}"
# 2) Build once
ironframe build --output dist/tailwind.css "src/**/*.{html,tsx}"
# 3) Build with template CSS and config
ironframe build -i src/app.css -c ironframe.toml -o dist/app.css "src/**/*.{html,tsx}"
# 4) Compare output with reference CSS
ironframe build -i src/app.css -o dist/app.css --compare-css dist/app.tailwind.css "src/**/*.{html,tsx}"
# 5) Watch mode with polling
ironframe watch --poll --poll-interval 250 -o dist/app.css "src/**/*.{html,tsx}"
Production note
ironframe targets Tailwind CSS v4.1-equivalent compatibility Validate generated CSS against your existing output and add regression checks in CI before a full rollout.
Previous
OSS ListNext
README / Full Specs