A Laravel frontend scaffolding preset that automatically sets up Inertia.js for building single-page apps.
laravel-frontend-presets/inertiajs is a Laravel package that provides a frontend scaffolding preset for Inertia.js. It automates the setup process required to integrate Inertia.js into a Laravel application, allowing developers to quickly start building single-page apps with server-driven routing and controllers. The preset eliminates manual configuration steps, streamlining the initial project setup.
Laravel developers who want to build modern single-page applications using Inertia.js without dealing with manual configuration. It's ideal for full-stack developers working on Laravel-based projects that require a seamless frontend-backend integration.
Developers choose this preset because it significantly reduces setup time and complexity when using Inertia.js with Laravel. Its automated scaffolding and Laravel-native integration provide a quick, opinionated starting point that follows best practices, allowing teams to focus on building features rather than configuration.
An Inertia.js frontend preset for the Laravel Framework
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Eliminates all manual configuration steps for Inertia.js integration, allowing developers to start building immediately with a single Artisan command, as highlighted in the README.
Leverages Laravel's routing and controller structure for server-side routing in SPAs, ensuring a native fit with existing Laravel workflows.
Uses `php artisan ui inertiajs` to set up the frontend stack in minutes, reducing initial bootstrap time and complexity.
Automatically discovered by Laravel without manual service provider registration, simplifying setup and maintenance.
Inertia.js is in early development, so the preset is in flux and may introduce breaking changes, making it risky for stable projects.
Requires Laravel 7.0 or higher, excluding older Laravel applications without upgrades, as noted in the usage instructions.
Imposes a specific setup that may not accommodate teams wanting full control over frontend tooling or custom build processes.