- How do I install Justd Laravel in a new project?
- You bootstrap it as a scaffold rather than installing it as a dependency: create a project from the repository using composer create-project or the GitHub template flow, then run npm install and start the dev server. There is no composer require step in the intended workflow, because the repository is a full Laravel application skeleton rather than a package. Treat the first clone as the moment you take ownership of the codebase.
- Is justd/laravel a Composer package I can require into an existing app?
- No. Despite the vendor/package naming, the repository is a Laravel skeleton application (Inertia v2, React 19, TypeScript) with a checked-in AGENTS.md, not a library published for dependency consumption. It has 0 dependents on the ecosystem side, which is consistent with a clone-and-own starter kit. If you need a drop-in component package, this is the wrong shape and you should look at Justd UI's React distribution instead.
- Which Laravel and PHP versions does Justd Laravel support?
- The scaffold targets Laravel 12's slim skeleton (bootstrap/app.php for middleware, exceptions, and routing; no Http or Console Kernel) and requires PHP 8.4. It will not drop into Laravel 10 or 11 projects, and teams pinned to PHP 8.3 or below cannot run it as-is. Confirm the exact version pins in composer.json before committing, since the stack is intentionally bleeding edge.
- What does the Justd Laravel stack include out of the box?
- It combines Laravel 12, Inertia v2 with React 19 and TypeScript, Tailwind CSS v4, Wayfinder for generated TypeScript route helpers, Sanctum v4 for authentication, Pest 3 with PHPUnit 11, Pint, and Sail for local containers. Laravel Boost v2 is wired in as an optional MCP server for agent-assisted development, alongside a well-specified AGENTS.md of conventions such as Form Requests for validation and eager loading by default. The Justd UI components are Tailwind-powered React components you compose directly in your pages.
- Can I add Justd Laravel to an existing Laravel application?
- Brownfield adoption is not supported: there is no service provider, config publish, or migration path to graft the scaffold onto a running app. The realistic approach is cherry-picking individual patterns into your codebase, such as the Wayfinder Vite plugin, the Pest and Pint configuration, or the AGENTS.md conventions. Expect to spend more time extracting pieces than you would spend configuring the official starter kit.
- How do I upgrade a Justd Laravel fork when Laravel releases a new version?
- There is no upgrade channel. Once you fork or create-project the scaffold, every upstream change becomes a manual diff-and-merge, and Laravel major upgrades are yours to perform. Plan for permanent ownership: pin your dependency versions, keep your customisations isolated in clearly marked directories, and track the upstream repository so you can pull selected commits deliberately rather than blindly.
- What testing and code style tooling ships with it?
- The scaffold includes Pest 3 on top of PHPUnit 11 for feature and unit tests, plus Pint for automated code style. Sail provides the local container environment, so the test suite runs against the same PHP and database versions as your team. The AGENTS.md conventions also spell out expectations around validation, Eloquent usage, and queued jobs, which makes the test setup unusually opinionated for a starter kit.
- How risky are the pre-1.0 dependencies like laravel/wayfinder and laravel/mcp?
- Several core dependencies are at v0, which means semver permits breaking changes in any minor release, and Wayfinder's generated route helpers sit on the critical path of every frontend request. Laravel Boost also gates parts of the developer workflow behind an MCP server that must be configured and reachable. Pin exact versions, review the changelogs before upgrading, and budget time for a Wayfinder breaking change rather than assuming stability.
- Who maintains justd/laravel, and is the release history reliable?
- That needs verification before adoption. The package name, the intentuilabs repository owner, and a description matching the official Laravel skeleton verbatim do not line up cleanly, and the latest release is dated in the future, which is a metadata anomaly. Confirm authorship, license, and copyright against Packagist and the repository tags, and ask whether this is a fork, a re-host, or an independent skeleton with a published support window.
- What are the alternatives to Justd Laravel?
- For a greenfield Laravel SPA, the official Laravel React starter kit covers most of the same ground with a clearer maintenance story, and Laravel Breeze or Jetstream remain solid options if you want first-party support. If you specifically want the Justd UI components, you can install them into any React or Inertia app without adopting this scaffold. Teams standardising on Blade, Livewire, or Vue should stay with their existing starter kit rather than fight this stack.