- How do I install yellow-three/daisyui-starter-kit in a new Laravel app?
- Use laravel new --using yellow-three/daisyui-starter-kit to scaffold a new application. It wires Livewire starter-kit generation, Fortify routes and config, Vite entries, and daisyUI 5 semantic-token defaults. Pilot v1.0.0 on a clean repository first and pin the package version.
- Does this package work with existing Laravel applications?
- The package is a Laravel starter kit and scaffolding integration, not a runtime library. It is aimed at greenfield Laravel applications rather than existing apps. For existing apps, treat it as a source of scaffold patterns and components, not a direct in-place upgrade.
- What Laravel, PHP, Livewire, Fortify, Node, Vite, and daisyUI versions are supported?
- The release notes do not state a compatibility matrix for Laravel, PHP, Livewire, Fortify, Node/Vite, or daisyUI. Validate the package against your team's target versions before adopting it. Because it targets daisyUI 5 semantic tokens, confirm that your templates and custom styles do not depend on older daisyUI classes.
- What is the 22/23 test result mentioned in the release notes?
- The TPM assessment flags a material inconsistency: the release notes say feature-deselection scenarios are all green while listing 22/23. Treat that as an open quality signal until the maintainers explain whether it is a known skip, a flaky test, or a real gap. Reproduce the scenario locally and inspect the generated diff before rollout.
- How does feature deselection work in this Laravel starter kit, and what are the risks?
- The installer uses @chisel marker-stripping to remove feature-specific Fortify flags, routes, and Vite entries when you deselect features. That approach is effective but fragile if markers move, duplicate, conflict during merges, or are edited by users. Verify both over-removal and under-removal by running auth smoke tests and frontend builds.
- Is the installer safe to run in a non-empty repository or multiple times?
- The notes do not clearly confirm that the installer is idempotent or safe to run in a non-empty repository. Start with a clean repository, pin v1.0.0, and inspect the git diff after each generation. Do not assume an existing application can be converted safely in place.
- Does the package include tests and CI, and will it pollute my application's CI?
- The Composer dist ships tests, a CI workflow, and phpunit.xml, which improves confidence in the release. Confirm the tests are runnable in your environment and that the included CI does not unexpectedly affect your application's CI. Also verify laravel new --using on Linux and Windows developer machines.
- What are the production and maintenance concerns for this starter kit?
- Runtime scaling risk is low because this is scaffolding, not a production runtime dependency. Maintenance is the bigger concern: the package must track Laravel, Livewire, Fortify, Vite, and daisyUI releases. The daisyUI 5 migration and @chisel marker system add upkeep, so assign an internal owner for upgrades, issue triage, and installer regression testing.
- Can I use this starter kit for admin panels and auth-ready application UIs?
- Yes, it is intended for fast scaffolding of admin panels and app UIs with prebuilt components and auth-ready layouts. It wires Fortify route and config plus Vite entries, and sets sensible daisyUI 5 defaults. Run application tests, auth smoke tests, and a frontend build to validate the generated UI before using it in production.
- What is the license and support model, and how should I handle upgrades from pre-1.0 versions?
- The provided notes do not state the license or support model, and the upgrade path from pre-1.0 versions is not documented. v1.0.0 gives a stable baseline, but support expectations remain unclear. Assign an internal owner and pin the package version while you document supported versions and upgrade guidance.