- How do I install laravel-frontend-presets/now-ui-dashboard?
- Install it with Composer, typically as a dev dependency, then run php artisan preset now-ui-dashboard and rebuild your front-end assets. The preset publishes Blade layouts, authentication views, and vendored Now UI Dashboard assets into resources/views and public/. Because the artisan preset command was removed in Laravel 7, confirm on a spike branch that the command actually registers on your target Laravel version before relying on it.
- Does this preset work with Laravel 11?
- The package advertises Laravel 11.x support, but the underlying php artisan preset command was a Laravel 5.5 to 6.x construct removed in Laravel 7 in favour of laravel/ui. It is unclear whether the service provider re-registers that command on modern Laravel or whether the 2024 release is only a metadata bump. Treat Laravel 11 compatibility as unverified and validate it with a one-day spike on your exact Laravel and PHP combination.
- Why do I get "Command preset is not defined" after installing?
- Laravel 7 removed the built-in preset command, so a package must explicitly re-register it through its service provider to make it available again. If the provider does not do that on your Laravel version, the command will not exist no matter how the package is installed. The cheap fallback is to copy the Blade stubs and assets directly from the GitHub repository, since the templates are the real value rather than the installer.
- Does this package include authentication views?
- Yes. The preset scaffolds a Now UI Dashboard admin interface with pre-built Blade views for login, registration, password reset, and email verification, plus a starter dashboard and layouts. It is designed for a classic server-rendered Blade stack rather than Inertia, React, Vue, or Livewire. You should still review the generated auth controllers and routes against your application's existing security requirements.
- Does it use Vite or Laravel Mix?
- The vendored assets are packaged for Laravel Mix, not Vite, and there is no npm provenance, lockfile, or tree-shaking involved. Adopting it in a Vite-native project means manually porting the CSS and JavaScript into resources/ with pinned npm versions. Expect to handle jQuery plugin load order explicitly and to replace any mix() helper calls with @vite.
- Can I remove the package after running the preset?
- Yes. This is a scaffolding artifact rather than a runtime dependency: once the preset publishes its views and assets, the generated code becomes yours to own and the package can be deleted from composer.json. The recommended sequence is to scaffold on an isolated branch, move the views into your own namespace, extract the assets into npm or Vite, then drop the dependency. Committing that result gives you a maintainable shell without version drift risk.
- Is Bootstrap 4 and jQuery a security concern in this preset?
- Bootstrap 4 and jQuery are past end-of-life, and themes of this generation commonly rely on inline scripts that conflict with a strict Content Security Policy. Before shipping, review CSP headers, add Subresource Integrity where relevant, remove inline scripts, and drop unused Bootstrap modules. You inherit the full Bootstrap 4, jQuery, Popper, and icon font bundle, so plan a hardening pass rather than assuming the defaults are production-ready.
- Will the preset overwrite my existing views?
- Publishing typically writes into resources/views/auth and resources/views/layouts non-interactively, which can overwrite files you have already customised. Run the preset on a throwaway app or isolated branch first and diff the output against your existing views. Only then merge the pieces you actually want into your application.
- What licence applies to the Creative Tim Now UI Dashboard assets?
- The Laravel preset wrapper and the vendored Creative Tim theme assets can have different licence terms, so check both the package licence and the upstream Now UI Dashboard terms. Creative Tim themes often require attribution or a commercial licence depending on how they are used. Confirm the MIT versus attribution question before distributing or shipping the generated admin interface.
- What are the alternatives to this Laravel frontend preset?
- For modern Laravel applications, laravel/ui, Laravel Breeze, or Jetstream are the maintained options, and they integrate cleanly with Vite and current Laravel releases. If you specifically want the Now UI Dashboard look, the most reliable route is to copy the Blade templates from this repository and rebuild the assets under Vite rather than depending on the preset command. This preset is not a good fit for Inertia, Livewire-first, or Vite-native stacks without manual porting.