- How do I install and configure nytodev/inertia-bundle?
- Install it with Composer using composer require nytodev/inertia-bundle, then follow the README to register the package middleware and set the root view. Configure shared props and the asset version source in the package config so Inertia responses have a consistent page payload. If you are upgrading from v3.1.0, v3.1.1 is only a Composer version bump with no application code migration.
- Which Laravel and PHP versions does nytodev/inertia-bundle support?
- The package is Composer-based and targets PHP 8.x, with Inertia.js protocol behavior tracked against inertia-laravel 3.x. The overview does not enumerate every supported Laravel release, so check the composer.json require block for the exact laravel/framework and PHP constraints. Test the middleware and response helpers on your Laravel version before upgrading production.
- Is nytodev/inertia-bundle a replacement for inertia-laravel?
- On a standard Laravel application, inertia-laravel is still the default choice. nytodev/inertia-bundle is best treated as a framework-light adapter or parity reference unless you have a shared package serving multiple PHP backends. Do not dual-adopt both without a specific reason, because the middleware and response behavior overlap.
- How do I return an Inertia response from a Laravel controller with this package?
- Use the package's Inertia response helper in your controller and pass the component name plus a props array. Laravel routing and controllers stay in place, so you do not need a separate API for page navigation. Keep shared data in config or middleware instead of repeating it in every controller action.
- How do I share props globally in Inertia Bundle?
- Shared props are added once through the package's shared data API or middleware and are included on every Inertia response. Use request-aware sharing for auth or user data, and keep static app configuration in the shared props config. Be explicit about optional and deferred props, because they follow the Inertia protocol's partial-reload semantics.
- How does asset versioning work in nytodev/inertia-bundle?
- The package sends an asset version with each Inertia page response. When that version changes after a deploy, the Inertia client performs a full reload rather than using stale cached assets. Set the version from your build manifest or deployment identifier to make cache-safe releases deterministic.
- Can I use nytodev/inertia-bundle with Vue, React, or Svelte?
- Yes. The package is server-side and pairs with any Inertia.js client adapter, including Vue, React, and Svelte. You still need the matching @inertiajs client package and a root view that mounts your app. Pin the client version so its protocol expectations match the server, especially around expiresAt and error shapes.
- How should I test Inertia responses and package upgrades?
- Assert the Inertia component and props returned by your controllers using Laravel's HTTP testing helpers. Add contract tests for merge, prepend, deep-merge, match-on, deferred, scroll, once, and error props, because protocol details have changed in patch releases. Snapshot the page payload and diff it across upgrades to catch drift before users do.
- What changed in v3.1.1 and is it a breaking change?
- v3.1.1 has no public API changes, but it contains silent behavioral changes. once()->until() expiresAt is now in milliseconds instead of seconds, empty errors serialize as {} instead of [], and X-Inertia-Reset keys are omitted from merge, prepend, deep-merge, and match-on props. Audit anything that parses expiresAt or asserts the errors JSON shape, and test infinite-scroll or paginated merge props.
- Is nytodev/inertia-bundle production-ready and well maintained?
- The technical evaluation flags nytodev/inertia-bundle as a single-maintainer project with a narrow contributor base, so bus factor and long-term support are the main risks. It also documents known gaps against inertia-laravel 3.x, so expect recurring parity patches rather than a one-off release. For production, pin versions, add protocol contract tests, and keep inertia-laravel or a custom adapter as a fallback if you are Laravel-only.