- What is hotmeteor/inertia-statamic used for?
- hotmeteor/inertia-statamic is an Inertia.js adapter for Statamic. It swaps Statamic's native Antlers/Blade rendering for Inertia responses so a Laravel + Statamic backend can serve a Vue or React front end from one codebase. Statamic remains the CMS for content authoring, while Inertia handles the delivery layer.
- How do I install hotmeteor/inertia-statamic in a Laravel app?
- Install it with Composer, publish its config, wire the Inertia middleware and client-side adapter, and map your Statamic routes and collections to Inertia page components. Content authoring in the Control Panel stays untouched, so the work is contained to the delivery layer. Pin the exact version, such as 0.2.1, rather than a caret range because the package is still 0.x.
- Which Laravel, Statamic, and Inertia versions does hotmeteor/inertia-statamic support?
- The package is 0.x and its release context does not assert a compatibility matrix for Laravel, Statamic, and Inertia major versions. Validate it against the exact versions in your target application before committing to it. Pin an exact package version and check the repository for any CI matrix or version constraints.
- Does hotmeteor/inertia-statamic support Statamic multisite and localized routes?
- Multisite and localized route resolution are not explicitly documented in the available release context, and the routing layer is still maturing. v0.2.1 fixed a URI lookup that could 404 legitimate content, but edge cases such as multisite, localized URLs, and nested routes may remain under-tested. Build smoke tests for those URLs before relying on the adapter in a multilingual or multisite site.
- Does hotmeteor/inertia-statamic support Inertia SSR?
- Inertia SSR support is not asserted in the package context, so treat it as something to verify in a timeboxed spike. Decide your SSR and caching posture before designing page components because that choice constrains component design. If SSR is required, confirm compatibility with your Inertia version and server setup first.
- How does hotmeteor/inertia-statamic resolve Statamic routes, redirects, and 404s?
- v0.2.1 changed route resolution to use an actual lookup so legitimate content is not incorrectly 404ed, which implies v0.2 had a naive or broken URI lookup. You should still explicitly test redirects, custom routes registered outside collections, taxonomy terms, and genuine 404 behavior. Build a route-parity checklist from your sitemap and crawl and automate it as a smoke test.
- Can I use hotmeteor/inertia-statamic alongside existing Antlers templates?
- Yes, the recommended migration is a delivery-layer change rather than a CMS migration. Introduce the package alongside existing rendering and migrate one route family, such as a single collection, at a time. Keep the Antlers implementation live as a fallback until parity is demonstrated, then decommission Antlers templates last.
- Is hotmeteor/inertia-statamic production ready?
- Treat it as a 0.x package with API stability risk and a small maintainer footprint. v0.2.1 is a single-commit patch from a first-time contributor fixing route resolution, which is a useful signal about the maturity of the routing layer. Adopt it in production only with exact version pinning, route smoke tests, and a clear rollback plan.
- Does hotmeteor/inertia-statamic affect content authoring in the Statamic Control Panel?
- Content authoring in the Statamic Control Panel is unaffected because the package changes the delivery layer, not the CMS data model. Blueprints, content, and CP workflows stay the same while Inertia replaces how front-end pages are rendered. That also means rollback is a routing and configuration change rather than a data rollback.
- How does hotmeteor/inertia-statamic work with Statamic static caching, Forms, and Search?
- Interaction with Statamic static caching and addons such as Forms and Search is not asserted in the release context, so validate each one in your target application. Static caching and any SSR choice can constrain how props and Statamic-managed meta tags are surfaced to your Vue or React components. Run representative tests for those addons before expanding route coverage.