Laravel Moonlight Laravel Package

Product Decisions This Supports

• Build vs. buy on frontend scaffolding. Moonlight is the "third option" between the official Laravel Breeze/Jetstream presets and a hand-rolled Inertia + Vue + Tailwind setup. Choosing it is a decision about spending engineering days on auth screens, layouts, and Tailwind config versus differentiating features.
• Frontend architecture commitment. Adopting it locks the codebase into Inertia + Vue 3 + Tailwind (server-driven pages, no separate API layer). That's a near one-way door for the app's life; the decision deserves explicit sign-off, not a default "yes" from a developer.
• Time-to-first-feature for greenfield work. The value is highest where you start new Laravel apps repeatedly — internal tools, admin panels, client starter kits, MVPs — and lowest for a single flagship product where two weeks of scaffolding is noise against a multi-year roadmap.
• Standardization across squads. A preset encodes conventions (page structure, component layout, dark mode, Tailwind theme). If you want consistency across several apps, forking this into an internal template repo is a cheaper route than writing a style guide nobody reads.
• Dependency-risk budgeting. Because Laravel presets publish source files into your repo, abandonment is a code-ownership cost, not a runtime outage risk. That changes the calculus: you can adopt a low-maintenance package here in a way you couldn't for a runtime library.
• Roadmap sequencing on stack evaluation. If Inertia + Vue is on the table at all, a preset is a cheap, reversible way to prototype that path before committing a quarter to it.

When to Consider This Package

Adopt (or fork) when:

• You're starting a greenfield Laravel app and the team already knows Vue and Inertia well enough to debug generated code.
• You want a working baseline — auth flows, layouts, Tailwind setup — in an afternoon rather than a sprint.
• You're building internal tools, admin dashboards, or MVPs where the UI is conventional and speed beats bespoke design.
• You intend to own and modify the generated files — which you will, by design.
• You're actively evaluating the Inertia + Vue path and want a working reference implementation.

Look elsewhere when:

• Laravel version currency matters. Last release January 2023 and a single maintainer means recent Laravel and Inertia major versions are on you to reconcile. Official Laravel starter kits are maintained by the core team; for a long-lived product, that support delta outweighs the extras here.
• Low signal is a blocker for your org. 142 stars and a stale release cadence mean no security patching guarantee, no vendor support, no SLA. Fine for a template; not fine as a dependency you can't modify.
• The stack is wrong for the product: Livewire, React, or Blade-only fits better; or you need API-first/headless because mobile or third-party clients are on the roadmap (Inertia is server-driven and serves that poorly).
• The team lacks Vue/Inertia fluency — "batteries included" becomes "batteries you can't service," and the debugging cost eats the scaffolding savings.

How to Pitch It (Stakeholders)

To executives: This is a starter kit, not a platform bet. It compresses the first week or two of a new Laravel + Vue application into a few hours by shipping authentication, layouts, and styling out of the box. The honest caveat: it's a small community project, last updated in early 2023, with one maintainer. We should treat it as a template we fork and own, not a vendor dependency — the code lands in our repository, so the downside is bounded to some upgrade labor, not an outage or a lock-in. Rough expected value is one to two engineer-weeks saved per new app; the cost is roughly half a day of version reconciliation on first use.

To engineering: One command gives you auth, layouts, Tailwind, and Vue pages wired through Inertia — after that the files are yours, with no runtime dependency to manage. Two practical notes: the preset predates recent Laravel and Inertia majors, so budget time to reconcile versions before you build on it; and benchmark it against official Laravel Breeze's Vue + Inertia variant, which is maintained. Use Moonlight if its extras (dark mode, richer layouts, opinionated structure) are worth the manual upgrade work — otherwise use it as a reference implementation and copy the parts you want.