- Is fsi/datasource-bundle a Laravel package?
- No. fsi/datasource-bundle is a Symfony bundle that registers the FSi DataSource component in Symfony's dependency injection container and exposes Twig rendering helpers. It contains no Laravel service providers, facades, or Blade integration, so it is not a Laravel package.
- Can I use fsi/datasource-bundle in a Laravel application?
- You can add it via Composer, but it will not integrate with Laravel's container or Blade templates. The bundle registers Symfony services and exposes Twig helpers, so Laravel would discard most of its code. The viable Laravel path is to adopt the underlying fsi/datasource component and write your own service provider and Blade renderer.
- Does fsi/datasource-bundle support Laravel 10 or Laravel 11?
- No. The package declares Symfony bundle classes and has no Laravel version constraints or framework integration. It does not support Laravel 10, Laravel 11, or any other Laravel release. Laravel compatibility would require a separate wrapper or reimplementation.
- Which PHP and Symfony versions does fsi/datasource-bundle support?
- The last tagged release is from September 2021, which likely pins Symfony 4 or 5 era constraints and older PHP versions. You must verify PHP 8.1–8.3, Symfony 6/7, Twig 3, and Doctrine compatibility in a sandbox before relying on it. If Composer requires ignore-platform-reqs to resolve, treat that as a stop signal.
- How do I install and register fsi/datasource-bundle?
- Install it with Composer and register the bundle in your Symfony Kernel or bundles.php, then configure datasource services through the bundle's DI extension. This is Symfony-specific setup; Laravel has no equivalent bundle registration step. The bundle provides minimal autoconfiguration around the FSi DataSource component.
- Is fsi/datasource-bundle actively maintained?
- No. The last release was 2021-09-02, and the repository shows no recent tags, CI coverage for modern Symfony or PHP versions, or meaningful community activity. With zero dependents and low stars, there is little downstream pressure for fixes. Treat it as dormant and evaluate the underlying component separately.
- What is fsi/datasource-bundle used for?
- It integrates the FSi DataSource component with Symfony to define reusable data sources for paginated, filterable, and sortable listings. Typical use cases are admin grids, search results, and API collections backed by Doctrine or custom sources. In Laravel, you would need to recreate that abstraction with query builders and API resources.
- How do I test custom data sources with fsi/datasource-bundle?
- You can unit test custom data sources by mocking the underlying FSi DataSource component and asserting the returned data, counts, and filters. The bundle's Symfony DI wiring is thin, so most meaningful tests belong around your data source classes, not the bundle itself. In Laravel, test your own provider or query builder implementation instead.
- What are alternatives to fsi/datasource-bundle for Laravel?
- For Laravel, use Eloquent or query builder scopes plus API resources, or a maintained grid or listing package such as Laravel DataTables or Spatie Query Builder. If you like the datasource pattern, implement a small DataProviderInterface and service provider yourself. Reimplementing 100–200 lines is often cheaper than carrying an abandoned Symfony bundle.
- Should I use fsi/datasource-bundle in production?
- Only after a short spike confirms that its Composer constraints resolve on your target runtime and that the abstraction earns its keep. The dormancy, Twig coupling, single-vendor governance, and lack of Laravel support are significant production risks. For Laravel, prefer a native implementation or a maintained package.