Weave Code
Pawsome Mary Laravel Package
bearny-codes/pawsome-mary
Pawsome Mary is a Laravel/PHP package from bearny-codes that offers a simple, framework-friendly way to bring its core functionality into your application, keeping integration clean and lightweight while fitting naturally into Laravel projects.
a paw(e)some laravel starterkit using mary-ui/daisy-ui, livewire and tailwind-css
Frequently asked questions about Pawsome Mary
- How do I install Pawsome Mary in a new Laravel project?
- Pawsome Mary is a starter kit rather than a consumable Composer library, so the intended path is to generate a new project from the repository instead of running composer require. Clone the repo or use it as a GitHub template, then install PHP and Node dependencies, configure your environment file, and run the frontend build plus migrations. Treat the resulting repository as your own project going forward, not as a dependency you upgrade.
- Can I add Pawsome Mary to an existing Laravel application?
- Integration into an established app is low-to-moderate because the kit assumes ownership of authentication, routing, the user model, and the frontend build. You can lift individual pieces such as OTP auth, passkeys, or the MaryUI components, but adopting the whole kit usually means rewriting your auth layer and component library. Unless you are already reworking authentication, scaffolding a greenfield project and porting your domain logic is the more realistic path.
- What Laravel and PHP versions does Pawsome Mary support?
- Confirm the supported matrix directly from the repository's composer.json and CI configuration, since the 0.5.x line is pre-1.0 and constraints can shift between releases. Verify that your pinned Laravel major version and PHP version are covered by a tested CI matrix before committing. If CI coverage is narrow or missing, budget time for your own compatibility spike.
- How does OTP registration work in Pawsome Mary?
- Registration uses OTP-based verification, which introduces a delivery provider dependency for email or SMS. The important thing to check in the source is whether delivery is abstracted behind a contract or hardcoded to a single provider, since that determines how easily you can swap or add channels. Plan for provider outages and rate limiting, because a failed OTP delivery will block new registrations.
- Does Pawsome Mary support passkeys and WebAuthn login?
- Yes, the kit ships with Laravel Passkeys, which depends on browser WebAuthn support and a relying-party ID tied to your domain. That makes configuration environment-sensitive, especially for staging, multi-domain, or white-label deployments. You should also define a recovery path for users who lose their passkey device, since the kit may not document one.
- Is Pawsome Mary production-ready?
- It is published as a 0.5.x starter kit, so pre-1.0 churn and breaking changes to auth flows and UI components should be expected. Production use is workable for teams already comfortable with Livewire, WebAuthn, and OTP delivery, provided you assign an owner to track upstream releases. Support is likely community-only and best-effort, so plan for in-house expertise rather than vendor SLAs.
- What UI and frontend stack does Pawsome Mary use?
- Pawsome Mary uses Livewire with Tailwind CSS and MaryUI, which wraps DaisyUI components. That gives you an opinionated Blade-based frontend with pre-wired auth screens and no JavaScript framework build to maintain. It suits teams already standardized on Livewire and Tailwind, and fits poorly with SPA-first stacks.
- How does Pawsome Mary handle roles and permissions?
- Authorization is handled by spatie/laravel-permission, so roles and permissions follow that package's well-established model. Before adopting, decide explicitly whether its role modeling matches your intended authorization design, since retrofitting a different model later is expensive. Because it is a widely used package, scaling and developer familiarity are generally not concerns.
- How do I keep my Pawsome Mary starter kit updated with upstream changes?
- A starter kit is a fork, not a dependency, so upstream fixes do not arrive automatically through Composer. Record a clear divergence point in version control and review upstream releases manually rather than blindly merging them. Expect each 0.x release to require reconciliation work, and re-evaluate the fork once the project reaches 1.0.
- Does Pawsome Mary work with Inertia, React, or Vue?
- No, Pawsome Mary is built around Livewire with Blade, Tailwind, and MaryUI rather than Inertia or a JavaScript framework. Teams on Inertia with React or Vue, or building API-first architectures, are a poor fit and would fight the kit's assumptions. If you need that stack, Laravel Breeze or Jetstream with Inertia are more natural starting points.
Weaver
How can I help you explore Laravel packages today?