- What is lartisan/laravel-preset and what does it install?
- It is a Composer package that scaffolds Laravel applications with a curated set of defaults and a TALL admin panel, so you skip repetitive setup and start building sooner. The TALL stack combines Tailwind CSS, Alpine.js, Laravel, and Livewire. Version 1.1.0 adds Livewire authentication components with live validation on top of the base preset. Review the changelog and the published files list to see exactly what lands in your application.
- How do I install lartisan/laravel-preset?
- Install it through Composer, then run the preset's install command to publish its stubs, configuration, views, and routes into your application. Presets of this kind are usually applied to a fresh Laravel application rather than a mature codebase with existing scaffolding. Confirm the exact command names and any post-install steps in the package README before running it against a project you care about. A throwaway test application is the fastest way to see what it generates.
- Which Laravel, PHP, and Livewire versions does lartisan/laravel-preset support?
- The v1.1.0 release notes do not state explicit version constraints, so the authoritative answer is in the require block of the package's composer.json on Packagist. Because the preset ships Livewire authentication components, verify that the supported Livewire major version matches the one already in your build pipeline. Check Laravel and PHP minimums before introducing it to an existing project, and run a clean dependency resolution to catch conflicts early.
- Can I use this preset on an existing Laravel application?
- Presets are designed to scaffold new applications, so applying one to an existing app can overwrite views, routes, migrations, and configuration you already depend on. If you only want the Livewire auth components, work in a staging branch and diff the published files against your current setup first. Keep your existing auth routes behind a feature flag until the new flows reach parity. Do not migrate production authentication without a tested rollback path.
- Does it conflict with Breeze, Jetstream, Fortify, or Sanctum?
- The release notes do not say which authentication backend the preset assumes, so coexistence with Breeze, Jetstream, Fortify, Laravel UI, or Sanctum has to be verified in a clean test app. These packages register routes, guards, middleware, and view namespaces that can collide with a preset's scaffolding. Sanctum is usually orthogonal if you only need API tokens, but route and view collisions remain the main risk. Check for duplicate route names and conflicting middleware groups after installing.
- How does live validation on the Livewire auth components work, and is it secure?
- Live validation sends field-level requests as the user types, which improves feedback but lets unauthenticated visitors trigger validation logic repeatedly. Confirm that the same rules are enforced server-side on final submit and are not merely reflected in the browser. Make sure login, registration, and password reset endpoints are rate limited and throttled, and that error messages do not reveal whether an email address exists. Authentication is a high blast radius surface, so treat these checks as mandatory before production.
- Are the Livewire auth components opt-in, or do they replace existing auth views?
- Version 1.1.0 is described as additive, but the notes do not state whether the components replace default auth scaffolding or are optional. Install into a throwaway app and inspect which views, routes, middleware, and config entries get published. If they are not opt-in, you can often keep your own screens by skipping publication or overriding the package's view namespace. Document what you override so future upgrades stay predictable.
- Are there tests covering login, registration, password reset, and email verification?
- The release notes make no mention of a test suite, so inspect the repository for a tests directory and CI workflow before relying on the components. Even if the package ships tests, run your own regression suite for login, registration, password reset, email verification, remember-me, session fixation, and CSRF. Also test with your real session driver, mail transport, and queue configuration. These tests are worth writing regardless of which auth scaffolding you use.
- How do I upgrade from an earlier version, and does the package follow semantic versioning?
- Version 1.1.0 is described as additive, which suggests backward compatibility, but that is an inference from the version number rather than documented evidence. Read the changelog and any stated deprecation policy, then diff the release tags to see which stubs, views, and config files changed. Republish only the assets you actually need and upgrade in a staging branch. Keep a rollback path until the auth flows pass your regression tests.
- What are the alternatives to lartisan/laravel-preset?
- For authentication alone, Laravel Breeze, Jetstream, Fortify, and the starter kits cover most needs, while Filament or Laravel Nova are common choices for admin panels. Laravel's own installer presets and community starter kits also scaffold projects with opinionated defaults. Choose based on whether you want the full TALL admin panel or just the Livewire auth components. Compare maintenance activity, Laravel version support, and test coverage before committing, since presets are hard to unwind later.