- Is cretueusebiu/laravel-vue-spa a Composer package, and how do I install it?
- No, it is a starter kit rather than a runtime library, so there is no dependency to pin or upgrade. You create a project from it or clone the repository, then run composer install, npm install, copy .env.example to .env, generate an app key, and migrate. From that moment the code is yours, which means adoption is really forking a scaffold, not installing a package.
- Which Laravel and Vue versions does laravel-vue-spa use?
- It is a 2021-generation scaffold: the last release was August 2021, it predates Laravel 9's Vite default, and it ships a Vue 2 lineage with Vue Router 3 and Vuex. Vue 2 reached end of life on 31 December 2023, and the pinned Laravel major is well outside its security-support window. Check composer.json and package.json in the repo for the exact pinned versions before committing to anything.
- Does laravel-vue-spa support server-side rendering or good SEO?
- No. It is a client-rendered Vue SPA with no SSR, so crawlable HTML and above-the-fold performance require a separate prerender step or a different architecture entirely. That makes it a poor fit for marketing and content sites and a reasonable fit for authenticated dashboards, multi-tenant consoles, and internal tools. Treat this as an architecture decision to make before cloning, not a configuration detail.
- What authentication mechanism does laravel-vue-spa use: session, Sanctum, or Passport?
- The kit advertises end-to-end auth flows out of the box, but that phrasing hides the critical fork between session-cookie, Sanctum token, and Passport-based auth. Which one it uses determines your CSRF story, your mobile and second-client story, and your CORS posture. Verify the mechanism in the code before designing endpoints around it, because swapping auth models later touches every route.
- Is cretueusebiu/laravel-vue-spa still maintained?
- Effectively no. The last release was August 2021, it is MIT licensed with roughly 3k stars, and it has a single maintainer with no LTS policy and no security disclosure process. That is acceptable for a scaffold you fork and own, but it is disqualifying if anyone on the team believes they are adopting a package with upstream support.
- How do I upgrade laravel-vue-spa to Vue 3 and Vite?
- Budget this as an adoption cost rather than a later nice-to-have. Expect Laravel Mix and webpack to Vite, Vue 2 to Vue 3, Vue Router 3 to 4, Vuex to Pinia, plus a Laravel major upgrade. Many teams find it faster to scaffold a fresh Laravel app with Breeze or Jetstream and port only the pieces of this kit they actually want.
- What is included in the laravel-vue-spa scaffold?
- It bundles the full vertical slice of a Laravel API plus Vue SPA product: client-side routing with Vue Router, centralized state with Vuex, authentication flows, an API surface, and a preconfigured asset build. That is genuinely convenient for a greenfield SPA. Audit which parts you actually want, though, because you inherit and own all of it, including the parts you will rewrite anyway.
- What does the asyncData hook in laravel-vue-spa do?
- Changelog material references an asyncData component hook with pages/home.vue, which reads like a Nuxt convention. In a Vue Router and Vuex SPA it is most likely a client-side prefetch hook that resolves data before route render, not server-side rendering. Confirm what it does and whether it is documented public API before building page patterns on it.
- Is laravel-vue-spa production ready, and how do I test it?
- It can reach production only after you modernise the dependency baseline, so treat the scaffold as a starting point rather than a shippable stack. On testing, Laravel provides PHPUnit or Pest for the API side and you can add Vitest or Jest with Vue Test Utils for components, but the 2021 tooling will not survive a Vue 3 migration untouched. Because you own the fork, decide your test coverage and CI setup as part of adoption, not afterwards.
- What are the best alternatives to laravel-vue-spa?
- Laravel Breeze and Jetstream with an Inertia or Vue frontend give you a maintained, current-generation starting point that tracks modern Laravel and Vite. If you need SEO-friendly content pages, Nuxt or Inertia with SSR is a better architectural fit than a client-rendered SPA. Also look for community forks of this kit rebuilt on Laravel 10 or 11 with Vite and Vue 3, and check their maintenance posture before relying on them.