Weave Code
Storia Bundle Laravel Package
iq2i/storia-bundle
A Symfony bundle for integrating Storia into PHP applications. It provides the service wiring and configuration needed to enable Storia features in a Symfony project, so you can install via Composer, register the bundle, and start using it without building custom integration code.
Storia Bundle integrates Storia into Symfony/PHP applications, providing a clean foundation for tracking and managing history around your domain entities. It wires configuration, services, and Doctrine hooks so you can record changes consistently without scattering audit logic throughout your codebase.
- Automatic Doctrine entity history tracking
- Configurable storage and history metadata
- Symfony service and configuration integration
- Extensible hooks for custom entities/workflows
- Simple Composer installation
Frequently asked questions about Storia Bundle
- Can I use iq2i/storia-bundle in a Laravel application?
- It is published as a Symfony bundle, not a Laravel package, so there is no supported drop-in path. Laravel lacks Symfony's bundle registration, DI extension, and Twig runtime assumptions. A Composer spike may work if the bundle exposes framework-agnostic PHP services, but the UI layer would likely need a Blade rebuild. Treat Laravel support as unproven until you verify it yourself.
- How do I install iq2i/storia-bundle with Composer in Laravel?
- You would run composer require iq2i/storia-bundle and then resolve dependency constraints, but Laravel pins several symfony/* components to Illuminate-compatible versions. The bundle may require symfony/framework-bundle, symfony/form, or symfony/twig-bundle, which Laravel does not install by default. Start with composer why-not against your Laravel version before writing integration code. If resolution fails, do not force it or override constraints blindly.
- Does Storia Bundle support Laravel 10, 11, or 12?
- The package metadata does not document Laravel version support, and its Symfony bundle conventions suggest Laravel is not the primary target. Laravel version compatibility depends on the exact symfony/* constraints in its composer.json and whether they collide with your Illuminate release. Verify with a one-hour Composer spike on your target Laravel version. There is no evidence base from dependents because the package has zero dependents.
- How does Storia Bundle track model changes and audit trails?
- The blurb describes story-style history for Laravel models: tracking every change, recording who edited what and when, and presenting a readable timeline. However, the package is evaluated as a Symfony UI bundle, so the actual tracking implementation may be coupled to Symfony services or presentation artifacts. Inspect the source for framework-agnostic model observers or event listeners before assuming Laravel Eloquent integration. If the logic is Twig or Form coupled, only the service layer may be reusable.
- Can Storia Bundle restore previous versions of a model?
- The overview claims you can restore previous versions and keep a clean timeline of your data. That capability would need to be implemented as a service that reads stored snapshots or diffs and writes them back to your Eloquent model. Because the package is Symfony-oriented, confirm whether restoration is exposed as plain PHP or tied to Symfony Forms and controllers. In Laravel you would likely wire it through a custom service or action class.
- Is Storia Bundle a good alternative to spatie/laravel-activitylog or Laravel Auditing?
- For Laravel, no—not as a drop-in alternative. Spatie activitylog and Laravel Auditing are Laravel-native, documented, and widely adopted, while Storia Bundle is a Symfony bundle with 15 stars and zero dependents. Storia may be useful as a design reference for story-style timelines, but adopting it wholesale adds cross-framework risk. Choose a Laravel-native package unless your spike proves Storia resolves cleanly and you accept rebuilding the UI.
- What are the Composer requirements and Symfony dependencies of Storia Bundle?
- The assessment flags likely constraints on symfony/framework-bundle, symfony/form, symfony/twig-bundle, and symfony/dependency-injection, plus a PHP version range. Laravel already pins symfony/console, http-foundation, process, finder, error-handler, and var-dumper indirectly through Illuminate. The first gate is running composer why-not iq2i/storia-bundle against your Laravel target. If it fails, the package is not integrable without forking or constraint overrides.
- Does Storia Bundle work with Blade, or does it require Twig?
- The -bundle suffix and UI focus suggest Twig templates and Symfony Form types are central, which do not port mechanically to Blade. A Twig bridge such as rcrowe/twigbridge is technically available, but it adds a second templating engine, escaping model, and cache layer. For a UI package that negates much of the value. The realistic Laravel path is to reuse any plain PHP services and rebuild the timeline UI in Blade or Livewire.
- How should I test Storia Bundle audit trails in a Laravel app?
- First test Composer resolvability and service container wiring in a throwaway Laravel app before writing feature tests. If the package exposes framework-agnostic services, unit test change capture and restoration with orchestration around Eloquent models. If it depends on Symfony runtime wiring, you cannot meaningfully test it inside Laravel without a bridge. Keep the spike isolated and time-boxed.
- Is Storia Bundle production-ready and actively maintained?
- The assessment shows 15 stars, zero dependents, and a 2026-03-30 release date, with no downstream ecosystem evidence. It is published by IQ2i, a French development agency, but release cadence and long-term support are unverifiable from the metadata. Single-vendor maintenance and no visible documentation increase risk. Ask the vendor about support arrangements and inspect the repository history before production use.
Weaver
How can I help you explore Laravel packages today?