- What is ambengers/kinetic used for in Laravel?
- Kinetic adds view-composer-style prop composition to the Inertia.js Laravel adapter. It lets you define composers against Inertia page or component names so page props are assembled in one place instead of being scattered across controllers, middleware, and shared props. It is aimed at Laravel apps that want explicit, convention-based prop composition for Inertia pages.
- How do I install Kinetic in a Laravel Inertia app?
- Install it as a Composer dependency and register the package service provider according to its documentation. You then define composers that target your Inertia page names. Because install effort is low, validate semantic fit first with a single non-critical page before broad adoption.
- Does Kinetic support Inertia deferred props, lazy props, partial reloads, and SSR?
- The package targets the Inertia Laravel adapter, but you should confirm support for deferred props, lazy props, partial reloads, and SSR before relying on them. The technical assessment flags these as key compatibility questions. Run a spike on a page that uses those features and assert the composed payload.
- How are Kinetic composers matched to Inertia pages, and how are props merged?
- Composers are registered against Inertia component or page names, so stable page naming conventions matter. Confirm how the package resolves names and whether shared props, multiple composers, and controller props override or merge, and in what order. Test collisions explicitly before moving shared or cross-cutting data into composers.
- Can Kinetic composers enforce authorization for page props?
- Composers can become the source of truth for page props, so authorization must be handled deliberately. The package does not remove the need for policies, gates, or controller checks. Avoid loading sensitive data by default and add contract tests that assert unauthorized users do not receive protected props.
- What testing helpers does Kinetic provide for asserting Inertia props?
- The provided context does not list specific testing helpers for Kinetic. Check the package documentation and source for assertion utilities before designing your test strategy. In practice, add contract tests around composed Inertia responses and verify props, authorization, and payload size.
- Is Kinetic safe to use with Laravel Octane and long-running workers?
- The technical review asks whether the package is stateless and safe under Laravel Octane. Before production use, inspect for static state, request-scoped caching, and container bindings that could leak between requests. Run an Octane test if your application uses it.
- What Laravel, PHP, and Inertia versions does Kinetic support?
- Exact supported versions are not listed in the provided context. Pin the package version and verify its Composer constraints and CI matrix against your production PHP, Laravel, and Inertia adapter versions. Confirm Inertia client and SSR compatibility if you rely on them.
- Is Kinetic actively maintained enough for production use?
- The package has a narrow maintainer base and a low star count, so adoption risk is moderate. The MIT license allows forking, but forking transfers maintenance ownership to your team. Review release history and responsiveness, and pin versions before committing broadly.
- What are the alternatives to using Kinetic for Inertia prop composition?
- No single drop-in alternative is named in the provided context. Developers often compare controller-based prop assembly, Inertia shared props, and middleware-based composition. Evaluate Kinetic against those patterns for page-name stability, merge rules, authorization clarity, and testability.