Weave Code
Nova Tailwind Laravel Package
optimistdigital/nova-tailwind
optimistdigital/nova-tailwind integrates Tailwind CSS with Laravel Nova, giving admin panel developers a modern utility-first styling layer for customizing Nova resources, dashboards, forms, and UI components. Build cleaner, more consistent Nova interfaces faster.
Tailwind loader for Laravel Nova.
Frequently asked questions about Nova Tailwind
- What is optimistdigital/nova-tailwind used for?
- It is a build-time Tailwind CSS loader for Laravel Nova, aimed at developers building custom Nova cards, tools, fields, and resource screens. It ships a Nova-aware Tailwind preset, a publishable CSS entry, and a thin Composer service provider so your components emit utility classes that match Nova's admin chrome. It has no runtime footprint, models, routes, or migrations, so it only affects your compiled CSS. It is not intended for application teams that merely install third-party Nova cards.
- Does optimistdigital/nova-tailwind work with Laravel Nova 4 and Nova 5?
- Compatibility with Nova 4.x or 5.x is not validated. The package was built for the Nova 3 era and its last release was 2021-11-12, so all of its assumptions about Nova internals and Tailwind behavior have aged. With an archived repo, zero dependents, and 55 stars, modern incompatibilities are likely to be undetected rather than absent. Treat it as unsupported on current Nova and test any custom components carefully, or own the Tailwind preset yourself.
- How do I install optimistdigital/nova-tailwind in a Laravel Nova project?
- Install it as a dev dependency with Composer, publish its CSS entry with vendor:publish, and extend your Tailwind config with the provided preset. Note that the vendor was later renamed, so you may need to require outl1ne/nova-tailwind instead of optimistdigital/nova-tailwind depending on which name resolves in your registry. It is a build-time package, so it should not be a production runtime dependency. Confirm the published assets land in the expected paths before wiring them into your mix pipeline.
- Does nova-tailwind work with Vite, or does it require laravel-mix?
- The published documentation assumes a laravel-mix and webpack pipeline, which many Laravel teams have since replaced with Vite. Because the package is essentially a Tailwind preset plus a CSS entry, you can usually port those pieces into a Vite build manually. There is no maintained Vite integration or updated docs, so expect to do that wiring yourself. If your Nova project already uses Vite, budget time for this migration friction.
- Which Tailwind CSS version does nova-tailwind target?
- It targets the Tailwind 2-era toolchain that was current when the package was last released in late 2021. Modern Tailwind 3 and later changed content and purge semantics and enabled JIT by default, which can break the preset's assumptions. Silent CSS purging can also fail open and be invisible in logs. Validate your compiled CSS output if you attempt to use it with a newer Tailwind major.
- Why is the Composer name optimistdigital/nova-tailwind when the repository is outl1ne/nova-tailwind?
- The vendor was renamed from optimistdigital to outl1ne, so the repository URL and the historical Composer name can disagree. This matters for lockfiles, SBOMs, and security scanner allowlists, which may flag one name but not the other. Document which name your project actually resolves so auditors are not confused. If you are migrating, check that your lockfile and allowlists are updated consistently.
- Is optimistdigital/nova-tailwind still maintained?
- No. The repository is archived and the last release was 2021-11-12, with 55 stars and zero dependents. That means there is no patch channel for Tailwind, PostCSS, laravel-mix, or Nova compatibility fixes. Treat it as a config snippet with a packaging wrapper rather than a maintained dependency. Decide explicitly who owns the code if you adopt it, and define an exit trigger.
- Can I use the Tailwind preset without installing the Composer package?
- Yes. The Composer wrapper is thin, and the meaningful deliverable is the Tailwind preset and CSS entry. You can lift the preset into your own tailwind.config.js and own the CSS entry directly, which removes the archived dependency from your graph. For most teams starting today, a first-party preset of a few dozen lines is a strictly better outcome. This also avoids the optimistdigital versus outl1ne naming ambiguity.
- Will nova-tailwind's preflight styles conflict with Laravel Nova's own CSS?
- Preflight conflicts are a known risk because Nova ships its own compiled stylesheet and reset. Double-preflight collisions can cause subtle layout drift or unstyled components that are hard to trace. Check whether the preset disables or inherits Tailwind preflight and test it against Nova's compiled CSS. Because these failures are visual rather than fatal, they will not appear in logs and need deliberate QA.
- What should I check before using nova-tailwind in production, and what are the alternatives?
- Confirm which Nova and Tailwind versions are actually validated, how preflight behaves, which Composer name your lockfile resolves, and who the named internal owner is. Define an exit trigger before adoption, since the package is archived and has no patch channel. The main alternatives are a first-party tailwind.config.js preset, Nova's own nova.mix.js tooling, or simply owning the CSS entry in-house. The blast radius is limited to admin UI regressions, not data loss or request-path security, so this needs an ownership decision rather than a full production-readiness review.
Weaver
How can I help you explore Laravel packages today?