- What is cretueusebiu/laravel-nuxt used for?
- It is a Laravel-Nuxt starter kit that integrates a Nuxt.js frontend with a Laravel API backend. It provides scaffolding, authentication support, and a workflow for server-rendered JavaScript apps backed by Laravel. Version 3.0.0 aligns with Laravel 8 and Nuxt 2-style architectures, so treat it as a legacy integration rather than a modern starter.
- Which Laravel versions does laravel-nuxt 3.0 support?
- Release 3.0.0 aligns the package to Laravel 8. The available evaluation does not confirm support for Laravel 9, 10, 11, or 12, and it should not be assumed. Because Laravel 8 is end-of-life, confirm Composer constraints and plan for dependency patching if you adopt it.
- Does laravel-nuxt work with Nuxt 3?
- The package targets a Nuxt 2-style Laravel-Nuxt architecture, not Nuxt 3. The evaluation recommends keeping any Nuxt 3 migration separate from a laravel-nuxt upgrade. For modern Nuxt 3 builds, evaluate direct Laravel API integration with Nuxt SSR instead.
- How do I install and configure laravel-nuxt?
- Install it with Composer and follow the starter kit scaffolding steps, then configure the Nuxt environment and API base URL for your Laravel backend. You must confirm the exact PHP, Laravel, Node, and Nuxt support matrix before upgrading. Validate authentication, session, CSRF, and API error behavior in a non-production environment first.
- What breaking changes are in laravel-nuxt 3.0 from v2?
- A 3.0.0 major release implies breaking changes, but the release notes are thin on migration steps and Nuxt compatibility. Expect possible config, middleware, dependency, and validation error response changes, including the validation catch added in issue #105. Review Composer lockfile changes and regression-test authentication and forms in a branch before rollout.
- How does laravel-nuxt handle authentication, sessions, and CSRF?
- The starter kit provides authentication scaffolding for a Laravel API backed by a Nuxt frontend, but session and CSRF behavior depends on your configuration and deployment topology. Verify cookie domains, session drivers, CSRF token handling, and API error responses between Laravel and Nuxt. Test login, logout, form submissions, and validation failures in a staging environment.
- Can I use laravel-nuxt for server-side rendering in production?
- It can be used for SSR only when your stack matches Laravel 8 and the compatible Nuxt version. SSR means Laravel and Node/Nuxt runtimes scale separately, so you need caching, CDN, health checks, and consistent build artifacts. The package glue is unlikely to be the main bottleneck, but it increases deployment coupling and failure modes.
- Is cretueusebiu/laravel-nuxt actively maintained?
- It appears community-supported with no vendor SLA, and Laravel 8 being end-of-life shifts maintenance burden to your team. Check GitHub activity, maintainer responsiveness, and whether a security policy exists before adopting it. Plan for dependency patching, possible fork ownership, and an explicit exit strategy if upstream stalls.
- What should I use instead of laravel-nuxt for Laravel 10 or 11?
- Do not downgrade a modern Laravel application to Laravel 8 just to use this package. For Laravel 10, 11, or 12, evaluate a maintained starter kit or integrate a Laravel API directly with Nuxt 3 SSR. Keep the Nuxt 3 migration separate from any laravel-nuxt upgrade decision.
- How are Laravel validation errors handled in laravel-nuxt?
- Issue #105 added a validation-error catch that reduces friction when handling Laravel form and API errors in Nuxt. However, validation handling changes can alter the client-facing error contract, so confirm whether the change is backward-compatible for your forms. Test 422 responses, field mapping, and user-facing messages before deploying.