Weave Code
Argon Laravel Package
laravel-frontend-presets/argon
Laravel frontend preset that swaps the default scaffolding for the Argon design system, giving you ready-made Blade auth views, layouts, and components. Install it to bootstrap a polished admin-style UI for new Laravel apps with minimal setup.
Laravel 11.x Front-end preset for argon
Frequently asked questions about Argon
- What is laravel-frontend-presets/argon and what does it actually do?
- It is a Laravel front-end preset that replaces the default scaffolding with the Argon design system from Creative Tim, a Bootstrap 4 admin-style UI. Running its Artisan command writes Blade auth views, layouts, components, controllers, routes, and frontend assets directly into your application. It is a one-shot code generator, not a runtime library, so once the files are emitted the package drops out of your dependency graph. There is no upgrade path afterwards: you either re-scaffold a fresh app or hand-merge diffs.
- How do I install the Argon preset in a new Laravel 11 application?
- The flow is to require the package with Composer in a throwaway or brand-new app, run the preset Artisan command, then run npm install and npm run build to compile the assets. Check the README for the exact command name, since preset packages vary between preset:xxx style and older conventions. Expect roughly half a day to two days for a greenfield spike including verification, and commit composer.lock and package-lock.json in the same commit. After scaffolding, review the generated auth views for parity with Laravel 11 conventions such as rate limiting, email verification, and password confirmation.
- Does laravel-frontend-presets/argon support Laravel 12?
- The package description targets Laravel 11.x, and Laravel 12 compatibility is not confirmed by the metadata provided. Before adopting it, verify the constraint in composer.json and test on the exact Laravel minor version you plan to ship. Because it is a scaffolding tool rather than a runtime dependency, an incompatible constraint shows up as an install failure rather than a runtime bug, which is at least easy to detect. Build a small compatibility matrix of Laravel version, PHP version, Node version, and asset pipeline rather than assuming.
- Does the Argon preset use Vite or Laravel Mix?
- This is a critical thing to verify before installing, because Laravel 11 defaults to Vite while older presets assume Laravel Mix and webpack. A Mix-era preset bolted onto a Vite app is a multi-day fix, not a config tweak, since you have to reconcile the build pipeline, entry points, and asset helper usage. Inspect the shipped package files such as webpack.mix.js versus vite.config.js before you run the scaffold. If it targets Mix, either downgrade your expectations or port the emitted assets to Vite by hand.
- Which files does the Argon preset overwrite in my Laravel app?
- Expect it to replace routes/web.php, a HomeController, and the resources/views/auth and resources/views/layouts trees, plus frontend assets such as CSS, JS, and SCSS. Treat the scaffold as a destructive operation rather than a merge, and run it on a clean branch or a fresh application so you can review the diff. Commit the generated output as your baseline immediately after install. That baseline commit is your safety net if anyone re-runs the preset later.
- Can I install the Argon preset into an existing Laravel application?
- You can, but you should not: it will clobber routes, controllers, and view directories you likely already own and have customized. The safer approach is to install it into a scratch Laravel 11 app, review the emitted views and layout, and port only the pieces you want by hand as a reference implementation. Retrofitting also multiplies the effort well beyond the half-day greenfield spike. Treat the preset as documentation of an Argon setup rather than a migration tool.
- Is laravel-frontend-presets/argon actively maintained, and what should I use instead?
- Maintenance signals are weak: roughly 234 GitHub stars, a small maintainer set, no commercial backing, and zero dependents, which is normal for scaffolding packages but means little ecosystem pressure to stay current. Laravel's official direction is starter kits like Breeze and Jetstream, which are Tailwind-first, Vite-first, and maintained by the core team. If your design system is Tailwind, those are the better default. Check the issue tracker responsiveness and the number of releases in the last twelve months before committing.
- Can I combine the Argon preset with Tailwind, Inertia, or Livewire?
- No, and you should not try. Argon is Bootstrap 4, so adding it to a Tailwind-based design system imports a second conflicting CSS framework, which is a permanent maintenance tax. It is also a poor fit for Inertia or Vue/React SPAs, Livewire-heavy apps that already use a component library, and API-only backends where it delivers zero value. It is a clean fit only for server-rendered Blade apps on Laravel 11+ with PHP 8.2+ and an npm asset build.
- What are the production risks of the Argon theme's Bootstrap 4 and jQuery stack?
- Argon is built on Bootstrap 4 and jQuery, and Bootstrap 4 is end-of-life upstream, so any future CVE or browser regression in that CSS and JS layer becomes your team's problem to patch. You are adopting a legacy frontend substrate for the sake of a ready-made admin aesthetic. Weigh that against how long the app must live and whether you can absorb periodic manual patches. A Tailwind-based starter kit avoids the EOL dependency entirely.
- Is the bundled Argon theme MIT licensed, or does it require Argon Pro?
- This must be verified before shipping, because the Argon design system from Creative Tim has both free and paid Pro variants. Confirm that every asset shipped by the preset is from the MIT or otherwise permissively licensed free tier, and that no Pro-only components, fonts, or illustrations are bundled. Check the LICENSE files in the package and the upstream Argon repository, and document the result for your legal review. If anything traces back to Argon Pro, substitute it before you go to production.
Weaver
How can I help you explore Laravel packages today?