- What is thepublicgood/vitamin and what problem does it solve?
- Thepublicgood/vitamin is an opinionated boilerplate package for using Vite with Laravel and InertiaJS. It was intended to wire Vite build tooling into Laravel and Inertia applications. The problem it addressed is now largely covered by official Laravel Vite tooling and Inertia's documented client/server setup. It is archived and not recommended for new or actively maintained applications.
- Is thepublicgood/vitamin still maintained and safe to use in a new Laravel project?
- No. The package was last released on 2022-08-15, is archived, has 49 stars, and reports zero dependents. There is no active upstream maintainer path for bug fixes, framework compatibility updates, or security patches. New Laravel projects should use the official Laravel Vite plugin and current Inertia guidance instead.
- Which Laravel, PHP, Node, Vite, and Inertia versions does thepublicgood/vitamin support?
- The provided information does not document a verified version matrix. Because the package is archived and last released in 2022, you should not assume compatibility with current Laravel, PHP, Node, Vite, or Inertia releases. Any evaluation must include a version-matrix spike and lockfile audit before commitment.
- How do I install thepublicgood/vitamin in a Laravel application?
- In a legacy application already pinned to compatible Laravel, PHP, Node, Vite, and Inertia versions, installation would typically start with composer require thepublicgood/vitamin. You then need to follow the package source or historical documentation for Vite config, Blade entrypoints, and Inertia root template changes. Because it is archived, freeze dependency versions and test the dev server, production build, SSR, and asset manifest behavior before relying on it.
- Does thepublicgood/vitamin support SSR, hot module replacement, and production asset manifests?
- This is not confirmed in the provided context and should be verified by source inspection and a spike. The package is a 2022-era boilerplate, so do not assume parity with current Vite or Laravel Vite plugin behavior. Check dev server HMR, production build output, SSR support, and manifest handling for your exact version combination.
- What are the alternatives to thepublicgood/vitamin for Vite in Laravel?
- Use the official Laravel Vite integration and Inertia's documented client/server setup. Laravel starter kits and current Inertia guidance cover the standard Vite, Blade entrypoint, and asset manifest workflow. These alternatives are maintained and documented, unlike the archived Vitamin package.
- Can I use thepublicgood/vitamin with a modern Laravel and Inertia application?
- Architecture fit is low for new or actively maintained Laravel and Inertia applications. The package would add a third-party layer between framework build tooling and application code with little compensating value. Modern applications should stay on the official Vite and Inertia path; only legacy applications already using Vitamin should consider containment.
- How do I migrate away from thepublicgood/vitamin?
- Freeze PHP, Node, Vite, Laravel, and Inertia versions, then inventory where the package is referenced. Create a branch using the official Vite, Laravel, and Inertia setup and migrate build scripts, Vite config, Blade entrypoints, Inertia root template changes, and environment behavior incrementally. Remove the package once dev server, production build, SSR, and asset manifest parity are proven.
- Does thepublicgood/vitamin modify Laravel bootstrapping, Blade root templates, or Inertia middleware?
- The provided evaluation flags this as a key question rather than a confirmed behavior. Inspect the package source before adopting it, especially for changes to application bootstrapping, Blade root templates, and Inertia middleware. Any such coupling increases migration cost and should be documented before legacy containment.
- Are there tests, CI evidence, or reproducible examples for thepublicgood/vitamin?
- The provided context does not include test or CI evidence, and the package has low stars, zero dependents, and an archived status. That combination suggests minimal ecosystem validation and limited real-world troubleshooting. Require CI evidence, a reproducible example, and a version-matrix spike before using it, even in legacy applications.