- What does laravel-frontend-presets/tailwindcss actually do?
- It is a Laravel frontend preset that replaces the framework's default Bootstrap scaffolding with Tailwind CSS equivalents. Running php artisan preset tailwindcss publishes a Tailwind config and overwrites package.json, webpack.mix.js, resources/sass, resources/js and the default auth views with Tailwind-styled versions. It is a scaffolding-time tool only and adds nothing at runtime.
- Which Laravel versions does this Tailwind preset support?
- It targets Laravel 5.5 through 6.x only, along with PHP 7.1–7.4 and the Laravel Mix webpack toolchain. Laravel 7 removed the underlying preset mechanism in March 2020, so the artisan command becomes inert on Laravel 7 and above. Do not expect it to work on Laravel 8, 9, 10, 11 or any Vite-based application.
- How do I install laravel-frontend-presets/tailwindcss?
- Install it as a dev dependency with composer require --dev laravel-frontend-presets/tailwindcss. Then run php artisan preset tailwindcss to swap the scaffolding, followed by npm install and npm run dev to build the assets. Apply it at project bootstrap on a fresh Laravel 5.5–6.x install rather than partway through an existing build.
- Which Tailwind CSS version does this preset ship with?
- The stubs pin Tailwind CSS 1.x era dependencies, which is what existed when the package was last updated in September 2020. Tailwind has since shipped multiple majors with breaking changes to its configuration model, including the shift to content globs and the CSS-first @theme approach in v4. Expecting Tailwind 3 or 4 semantics from these stubs will not work without manual rewriting.
- Is laravel-frontend-presets/tailwindcss still maintained?
- No. The package has been abandoned since September 2020 and has zero dependents, so nothing has forced it to stay current. Treat it as vendored code owned by your own team if you adopt it on a legacy project. Any Tailwind or Laravel upgrade becomes a manual, team-funded effort because there will be no upstream fixes.
- What should I use instead of this preset for Tailwind in Laravel?
- For anything on Laravel 7 or newer, skip this package entirely. Install tailwindcss, postcss and autoprefixer as dev dependencies, run npx tailwindcss init -p, set your content globs, add the @tailwind directives to your CSS and wire it into Vite via laravel-vite-plugin. If you specifically need auth scaffolding, Laravel Breeze already ships with Tailwind as its default styling.
- Can I apply this preset to an existing Laravel application?
- No, brownfield retrofit is not supported. The preset assumes a fresh scaffold and overwrites files wholesale, so applying it to a running app means manually diffing stubs against your customizations. That manual merge is exactly where most breakage occurs, and it is safer to hand-port only the Tailwind config and auth view styles you actually need.
- Does this package affect production runtime or performance?
- It is a dev-only, scaffolding-time artifact and ships nothing to production. Its only surface area is the php artisan preset tailwindcss command, which edits build config and view files once. Any performance or scaling concerns come from your own compiled assets, not from this package.
- Will npm install work with modern Node versions when using this preset?
- It is risky. The stubs pin 2020-era dependency majors built for Node 10–14 and webpack 4 via Laravel Mix, which is itself deprecated. On current Node releases the install may either resolve ancient transitive packages with audit advisories or fail outright. Pin your lockfile and run dependency scanning before committing to this stack.
- Does this preset replace Laravel's default auth views?
- Yes, it replaces the default auth views and frontend assets with clean Tailwind-styled templates. That said, if auth scaffolding is your actual requirement on a modern Laravel version, Breeze is the maintained first-party answer. Use this preset only when you are pinned to a legacy Laravel 5.5–6.x codebase and need the styling swapped in one command.