- What is chandanshakya/mary-ui-starter-kit and how do I install it?
- It is a Laravel application scaffold, not a library, that generates a new project wired around Mary UI, the Tailwind and daisyUI component set for Blade and Livewire, with Volt, authentication and roles included. You consume it once with laravel new or composer create-project rather than composer require, and the generated code becomes your own first-party repository. Pin the exact tag, for example v1.0.2, in the create-project command and record the provenance commit hash in your README so you can diff against upstream later.
- Can I install this starter kit into an existing Laravel application?
- Realistically no. It is designed for greenfield projects, and the practical integration path is generating a fresh app, stripping what you do not need, and porting your own domain logic in. For a project that is already mid-flight, cherry-pick individual Mary UI components and config values instead of attempting a retrofit.
- Which Laravel, PHP, Livewire and Tailwind versions does the starter kit pin?
- That is not documented in the release notes, so check composer.json and package.json on the tagged release before you commit. Starter kits are frequently pinned to the newest Laravel minor, which can force a runtime upgrade on your platform. Confirm whether it targets Livewire 3 or 4 and Tailwind 3 or 4, since those majors move fast and break scaffolds.
- What authentication and role management does the starter kit include?
- It ships auth scaffolding plus a roles layer, but the available notes do not say whether those flows are Breeze, Jetstream or Filament derived. Review the generated login, registration and password reset code line by line, and confirm what it assumes about your user model and role storage. Treat any seeded credentials or default admin accounts as untrusted until you have reviewed and replaced them.
- Is this starter kit a good fit for a production application?
- It fits internal admin panels, back-office CRUD and small SaaS consoles well. It is a weaker fit for public-facing, SEO-critical or heavily client-stateful applications, because Mary UI implies a server-driven Livewire and Tailwind frontend model. Weigh the single-maintainer bus factor as well before betting a long-lived product on it.
- Does the starter kit receive updates, and how do I upgrade it?
- There is no supported upgrade channel between minor versions. Once generated, the code is effectively a fork, and upstream improvements arrive only if you manually merge them. Plan for that at adoption time by keeping a clean initial commit, documenting the upstream tag and commit hash, and re-basing deliberately rather than expecting composer update to help.
- What actually changed in v1.0.2 of this package?
- The v1.0.2 release notes contain only an auto-generated compare link with no changelog body, so no functional delta is documented. Pull the diff against v1.0.1 and classify it as cosmetic, dependency bump or behavioral before you pin it. A bare changelog on a patch release is a weak transparency signal for a scaffold you may never cleanly re-base.
- Does the starter kit include tests, static analysis or CI?
- That is not stated in the available documentation, so inspect the generated project for Pest or PHPUnit suites, Larastan or Pint configuration, and CI workflow files. Many starter kits scaffold only UI and auth and leave quality tooling to you. If tests are missing, add them before building features on top of the scaffold.
- How does mary-ui-starter-kit compare to Laravel Breeze, Jetstream or Filament?
- Breeze and Jetstream are first-party scaffolds with broader maintenance and clearer upgrade stories, while Filament is a full admin panel framework. This package is a small, lightly adopted personal starter positioned around Mary UI components, so choose it when Mary UI is already your component library of choice. Otherwise the first-party options carry less bus-factor and version-coupling risk.
- Is the package actively maintained and what license does it use?
- It is a personal starter kit from a single maintainer, so bus factor is the primary risk to plan around. Check the repository for a license file and for observable issue response before committing. If your team needs a stable long-term vendor relationship, this package is unlikely to provide one.