- How do I install Artisan UI in a Laravel application?
- Install yungifez/artisan-ui with Composer in a Laravel application, then confirm service-provider registration, publish any configuration and assets, and verify the version constraints in composer.json. Start in a staging or low-risk admin module before rolling it out broadly.
- Which Laravel and PHP versions does Artisan UI support?
- Check the package composer.json for the supported PHP and Laravel constraints before installing; the context does not list exact versions. The package is positioned for standard Laravel applications using Blade and Composer, so verify compatibility with your current framework version in staging first.
- Do I need Tailwind CSS and Alpine.js to use Artisan UI?
- Yes. The package is described as a shadcn-inspired UI library for Laravel Blade using Tailwind CSS and Alpine.js, so your front end should already use or accommodate those tools. Confirm asset-publishing steps and CSS expectations before adopting it in an existing admin theme.
- Is Artisan UI suitable for API-only or headless Laravel applications?
- Artisan UI is a poor fit for API-only, headless, or non-Blade front ends because it operates at the Blade and view layer. It is best suited to monolithic Laravel applications that need an admin or CRUD interface.
- How do I publish and version Artisan UI assets behind a CDN?
- Publish the package assets as part of your deployment and verify how asset tags are emitted in your environment. The v1.3.6 per-request asset-tag change improves cache-busting and dynamic versioning, but if you use full-page or response caching, ensure cache keys vary appropriately or disable caching for views that emit asset tags.
- Can Artisan UI run destructive Artisan commands in production?
- Artisan UI provides a web dashboard for browsing and running Artisan commands, so treat it as an admin tool and protect its routes with authentication and authorization. Restrict or gate destructive commands in production and use environment-specific safeguards; review package maturity and documentation depth before relying on it for critical operations.
- Does upgrading to v1.3.6 change table sorting behavior?
- The v1.3.6 table-sort fix changes behavior when user-selected sorts are combined with builder defaults, aligning results with expected UX. No public API break is indicated, but test any tables that rely on the builder’s order overriding the chosen sort before upgrading.
- How is Artisan UI tested and maintained?
- Artisan UI is an open-source GitHub package with community support indicated rather than commercial support. Pin the version in composer.json, review release notes, confirm test coverage and release cadence, and keep an internal patch or fork strategy if the package becomes critical.
- What should I consider before adopting Artisan UI over building my own admin UI?
- Compare Artisan UI with building custom Blade admin screens or adopting a broader Laravel admin panel package, depending on whether you need command execution, CRUD tables, or both. Evaluate documentation depth, maintenance activity, Laravel version support, and how much UI you want the package to own.
- How do I test Artisan UI after installation or upgrade?
- Upgrade in staging first, then run regression tests on tables with custom sorts and on asset delivery behind any CDN or response cache. For a fresh install, validate a single low-risk admin screen, confirm sorting and asset loading, and then expand to broader workflows.