- What Laravel versions does rogervila/laravel-legacy-ui support?
- It is positioned as legacy UI and auth scaffolding for Laravel 8, with the evaluation also considering Laravel 9. The last release was in February 2022, so you must verify Composer constraints against your exact Laravel and PHP versions before installing. It is not recommended for Laravel 10 or newer or for API-first applications.
- How do I install and publish the legacy auth views?
- Install the package with Composer and run its Artisan commands to publish the legacy auth views into your application. The evaluation recommends doing this first in a disposable Laravel 8 or 9 app or a branch so you can diff the generated files. Review routes, controllers, middleware, and assets before merging the scaffold into your main codebase.
- Is rogervila/laravel-legacy-ui a fork of laravel/ui?
- The public context describes it as restoring Laravel's classic Bootstrap UI and auth scaffolding, but it does not confirm whether it is a direct fork of laravel/ui. Treat it as a legacy scaffolding tool and compare its generated output with laravel/ui in a sandbox. That diff will show how far it has diverged and what you must own.
- Does it conflict with Breeze, Jetstream, Sanctum, or laravel/ui?
- It can conflict with those packages because auth scaffolding often registers similar routes, middleware, views, and frontend presets. The evaluation specifically flags potential conflicts with laravel/ui, Breeze, Jetstream, Sanctum, existing routes, and asset builds. Use a fresh app or remove competing auth scaffolding, then check route names and middleware carefully.
- Is this package safe for production authentication?
- Authentication is security-sensitive, and this package has had no release since February 2022, so it should not be treated as a strategic platform dependency. The generated login, registration, password reset, and email verification flows must be reviewed, tested, and owned by your application team. Use it as a one-time scaffold and patch the generated code as needed rather than relying on upstream security updates.
- Does it support password reset, email verification, and rate limiting?
- The package is intended to restore Laravel's classic auth scaffolding, which normally covers login, registration, and password reset views. Email verification and rate limiting depend on the generated controllers, routes, middleware, and Laravel version, so verify each flow in your app. Add tests for reset tokens, verification links, throttling, and session behavior before production.
- Can I remove the package after scaffolding?
- Yes, that is the safer adoption pattern if the Artisan commands publish the auth views and related files into your application. The evaluation recommends considering removal after scaffolding to reduce long-term dependency risk. Keep the generated code under version control and confirm that no runtime package code is still required.
- Can I use rogervila/laravel-legacy-ui with Laravel 10 or Laravel 11?
- It is not recommended for Laravel 10 or newer or for teams standardizing on Breeze or Jetstream. The package is aimed at Laravel 8/9 legacy UI needs and had its last release in 2022. For modern Laravel versions, use the current first-party auth scaffolding and verify Composer constraints before attempting anything.
- What frontend presets and Bootstrap assets does it include?
- It restores Laravel's classic Bootstrap-based UI, so it targets Blade auth views with Bootstrap styling rather than Tailwind-based Breeze or Jetstream presets. Review the generated asset references and build steps against your frontend tooling, especially if your app uses Vite or modern asset bundling. The package is legacy and may not match current frontend defaults.
- What is the maintenance and security patch path for this package?
- Expect community-only support with no vendor SLA, a last release in February 2022, and limited package health. If generated code is copied into your application, maintenance shifts to your team; if the package remains a runtime dependency, pin the version or commit and plan to fork under MIT if needed. Set a review date and document ownership of the auth code.