- What is m2s/laravel-nuxt used for?
- m2s/laravel-nuxt is an opinionated integration layer that lets a Laravel app own the HTTP entry point while delegating rendering to a Nuxt SSR process. It ships a service provider, publishable config, routing and middleware that forward requests to the Node SSR server, plus Artisan tooling to scaffold or run the Nuxt side. It is not a headless API package; it assumes Laravel still front-doors the app, so PHP handles auth, persistence, and routing while Node handles SSR and assets.
- How do I install m2s/laravel-nuxt?
- Install it with Composer, then publish the package config, provision a Nuxt application, point the package at your Node server, and wire up the build and start scripts. The mechanical setup is straightforward; the real cost is environmental, since production needs Node alongside PHP-FPM, a process supervisor, and a build step in CI. Run it in a throwaway spike first to confirm version compatibility before adding it to a real app.
- Which Laravel and PHP versions does m2s/laravel-nuxt support?
- The package targets Nuxt 2-era Laravel integrations, and its published constraints appear stale relative to current Laravel and PHP releases. The technical evaluation flags framework version drift as a primary risk, so check the actual composer.json constraints and validate against your target LTS rather than assuming support. Pin Laravel, PHP, Nuxt, Node, and @nuxtjs module versions aggressively.
- Does m2s/laravel-nuxt support Nuxt 3?
- Almost certainly not without a rewrite. The package is built around Nuxt 2's SSR model, which is incompatible with Nuxt 3's Nitro-based architecture. Nuxt 2 is also end-of-life, so teams standardized on Nuxt 3 should treat this package as out of scope and plan an exit or a custom integration instead.
- How are sessions, cookies, and CSRF handled between Laravel and the Nuxt SSR server?
- The package forwards requests from Laravel to the Nuxt SSR process, so cookie, session, CSRF, and authenticated-request propagation must be handled deliberately across the PHP-to-Node boundary. This is one of the four risk areas identified in the evaluation, and the semantics are not something to assume work by default. Test authenticated flows explicitly, including CSRF tokens and session cookies, before relying on it for customer-facing paths.
- How do I deploy a Laravel plus Nuxt SSR app to production with this package?
- A typical production model is Laravel behind PHP-FPM with a supervised Node SSR process (PM2, systemd, or a Docker sidecar) and a Nuxt build step in CI. The package does not appear to include built-in process supervision or health management, so you own that layer. Validate on your exact PHP and Node base images rather than only locally.
- Is m2s/laravel-nuxt actively maintained and safe to use in production?
- Signals are weak: roughly 19 stars, zero dependents, a single-maintainer footprint, and an overall score of 1.9. That profile implies low battle-testing and no reliable security-patching path. If you adopt it, vendor it via a fork with pinned constraints and budget for maintaining the service provider and middleware yourself.
- Does m2s/laravel-nuxt fall back to SPA rendering if the Node server is unavailable?
- That behavior is not documented, and the package provides no built-in supervision or health management for the SSR process. If you need graceful degradation to SPA or client-only rendering when Node is unavailable, you will have to implement that fallback yourself, for example inside the forwarding middleware. Treat it as a design requirement to validate in a spike, not a guaranteed feature.
- What are the alternatives to m2s/laravel-nuxt?
- Common alternatives include a hand-rolled middleware and proxy of roughly 200 lines that you own, Inertia.js with Vue if your team is already Vue-centric, or a fully headless setup where Laravel exposes APIs and Nuxt deploys independently. The evaluation recommends comparing the package against a thin custom integration before adopting it as a dependency. If your team is on Inertia plus Vue, this package adds a runtime for little gain.
- Can I add m2s/laravel-nuxt to an existing Laravel Blade application?
- It is a poor fit for retrofitting an existing server-rendered Blade application with heavy session and CSRF coupling. The package assumes Laravel owns the entry point and the frontend is Nuxt, which is a hard mismatch for a mature Blade app. If you do adopt it, introduce it into one bounded surface such as a marketing site or admin sub-app before any core customer path.