- Is innocenzi/laravel-vite still maintained?
- No. The repository is archived, its last release was published on 2023-02-16, and the project is effectively in maintenance mode with a bus factor of one. It predates Vite 5, so newer Vite majors are not tracked. On Laravel 9.19 and above you should use the first-party Vite integration shipped with the framework instead.
- How do I install innocenzi/laravel-vite in a Laravel app?
- Install the package with Composer and publish its configuration file using Laravel's vendor:publish command, which creates config/vite.php. You then add a matching npm Vite plugin and point your vite.config.js at the same build directory and manifest. Installation is mechanically trivial, but because the package is archived it should only be installed in existing legacy applications already pinned to a compatible Laravel and Vite version.
- Which Laravel and Vite versions does innocenzi/laravel-vite support?
- The package fits Laravel 8.x through roughly 9.18, paired with Vite 2 to Vite 4. It does not support Vite 5 or later because the last release predates changes to the manifest schema and dev-server contract. Treat that compatibility window as a hard gate, not a preference: outside it the package is either redundant or unsupported.
- What is the difference between innocenzi/laravel-vite and Laravel's built-in Vite support?
- Laravel 9.19 and later ship a first-party Vite class, an @vite Blade directive, and the laravel-vite-plugin npm package that supersede this community package. Both approaches read public/build/manifest.json, use a public/hot file for hot module replacement, and expose Blade directives plus asset helpers. The framework version is maintained by the Laravel team, receives fixes, and tracks current Vite releases.
- How do I migrate from innocenzi/laravel-vite to laravel-vite-plugin?
- Replace the community npm plugin with laravel-vite-plugin and rewrite vite.config.js entry points, build.outDir, build.manifest, aliases, and any server proxy or host settings that previously lived in config/vite.php. Remove the package's service provider registration and config/vite.php so the framework's Vite class takes over. Most @vite(['resources/css/app.css', 'resources/js/app.js']) calls keep the same signature, but verify @viteReactRefresh, custom build directories, hot-file semantics, and programmatic uses such as Vite::asset() before deploying. Regenerate public/build, confirm the manifest keys, and make sure public/hot is git-ignored and absent from the deploy artifact.
- Does innocenzi/laravel-vite support hot module replacement?
- Yes. The package includes a dev-server client that reads public/hot, so running the Vite dev server refreshes assets in the browser during development. The first-party Laravel integration uses the same public/hot mechanism, which is why migrating mostly comes down to swapping the config and npm plugin. Ensure public/hot stays git-ignored and never ships in production builds.
- Is it safe to use innocenzi/laravel-vite in production?
- The runtime surface is small and mostly build-time, but the package is archived, so there is no CVE triage and no patched release if an issue is found. It becomes an unpatched dependency in your lockfile and will appear in SBOM and licence scans. Freeze the version, document it as technical debt with an owner and a migration date, and plan to exit rather than adding it to new projects.
- Can I use innocenzi/laravel-vite on Laravel 10 or Laravel 11?
- There is no reason to. Laravel 9.19 and later already include the first-party Vite integration, and on those versions both the framework and this package attempt to register the @vite directive. Whichever registration wins depends on service provider load order, which produces silent, environment-specific failures. On Laravel 10 or 11, remove the package and use the built-in directives with laravel-vite-plugin.
- Does innocenzi/laravel-vite support server-side rendering (SSR)?
- It has an SSR path, but it was the least-exercised part of the package and the project is archived, so it receives no fixes. If you rely on SSR, the safer route is the first-party Laravel Vite integration, which is actively maintained. Audit your SSR entry points before migrating and re-test rendered markup, not just client-side hydration.
- What should I use instead of innocenzi/laravel-vite?
- Use the first-party Laravel Vite integration on Laravel 9.19 or later together with the laravel-vite-plugin npm package. If you are stuck on Laravel 8.x, upgrade the framework first rather than adopting an archived package for a greenfield build. Inventory any starter kit, CMS, or legacy app that still requires this dependency and migrate it in a single scheduled window.