- Is creativspeed/inertia-bundle for Laravel or Symfony?
- It is a Symfony bundle, not a Laravel package. The repository describes an Inertia.js server-side adapter for Symfony 8 with Twig helpers, AbstractBundle integration, and Symfony-style configuration. Laravel applications should use the official Inertia Laravel adapter instead.
- Can I use creativspeed/inertia-bundle in a Laravel application?
- No. The package is built around Symfony 8 and Twig, so its bundle registration, root template, and service wiring do not apply to Laravel. For Laravel, use the official Inertia Laravel adapter and its Laravel-specific testing and middleware support.
- How do I install creativspeed/inertia-bundle in a Symfony 8 app?
- Install it with composer require creativspeed/inertia-bundle. With Symfony Flex it should auto-register; otherwise add CreativSpeed\InertiaBundle\InertiaBundle to config/bundles.php. Then create config/packages/inertia.yaml with settings such as version, root_view, and ssr options.
- Which Inertia.js frontend client version is required by creativspeed/inertia-bundle v2.0?
- The v2.0 technical assessment says the backend now targets the Inertia.js v3 protocol, including always, deferred groups, and merge or deep-merge props. You need a v3-compatible frontend client; a v2.0 backend paired with a v2 client can fail at runtime. Verify the installed package version and client compatibility because older README text may still reference v2 protocol.
- Does creativspeed/inertia-bundle support SSR and per-page SEO tags?
- Yes. The v2.0 assessment highlights a real SSR body and head hand-off to the Twig shell, so per-page title, meta, and canonical tags can be rendered server-side. Enable SSR in the inertia.yaml configuration and run the SSR service. This makes SSR viable for SEO-sensitive Symfony pages rather than only a client-side patch.
- Why does creativspeed/inertia-bundle v2.0 redirect with 303 instead of 302?
- Inertia requires 303 on non-GET redirects so the browser re-issues a GET after a PUT, PATCH, or DELETE. The bundle now converts these redirects automatically, which fixes hand-rolled or missing 303 handling. Tests or downstream clients that assert on 302 may need updates.
- How does Vite asset versioning work in creativspeed/inertia-bundle?
- The bundle supports Vite integration with automatic version detection and can use a configured version such as the APP_VERSION environment variable. The v2.0 assessment says asset-version conflict handling is now in-package, reducing stale-manifest and 409-style failures common in from-scratch integrations. Expect asset-version changes to trigger reload behavior when versions conflict.
- How are auth user and flash data shared by creativspeed/inertia-bundle?
- Auth data and flash messages are shared automatically on every Inertia response, removing much of the manual boilerplate from earlier integrations. Use InertiaAuthUserInterface to exclude sensitive user fields because automatic sharing sends the default payload unless you curate it. This makes field-level filtering more important, not less.
- How do I test Inertia pages with assertInertia in Symfony?
- The bundle provides an assertInertia testing helper for Symfony tests. Use it to assert the Inertia component and expected props instead of only checking HTML. When upgrading to v2.0, update tests that expect 302 redirects and account for deferred, grouped, or merged props.
- What are the history encryption risks in creativspeed/inertia-bundle v2.0?
- The new encryptHistory() and clearHistory() capabilities can encrypt page state stored in browser history, which helps with privacy reviews and PII concerns. Encryption depends on application secret key management, so plan key rotation and treat loss of the key as a data-loss event for history state. Call clearHistory() on logout as required hygiene so sensitive back-button state is not retained.