- Is fi/bootstrapitaliabundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, indicated by the Bundle naming convention and the ComuneFI origin, and it registers through Symfony's bundles.php and dependency injection container. The package description states it is a Bootstrap Italia bundle per Symfony. There is no Laravel service provider, facade, config file, or Blade view set to consume. Treat it as a Symfony-only package.
- Can I use fi/bootstrapitaliabundle in a Laravel application?
- Not in any direct way. Laravel has no Symfony bundle lifecycle, so the bundle's extension class and Twig namespaced paths will not be resolved by Laravel service providers. Blade cannot render Twig templates without a bridge such as rcrowe/twigbridge, which adds more risk than the wrapper removes. The only portable surface is the static Bootstrap Italia CSS, JS, and SCSS, which you can get from the upstream distribution.
- How do I install fi/bootstrapitaliabundle with Composer?
- You can install it with Composer, but only inside a Symfony application where you register it in config/bundles.php. There is no Laravel package discovery, so Composer will not auto-register anything useful in a Laravel project. For Laravel you should not install it as a dependency at all. If you only need the design system, install bootstrap-italia from npm or the CDN instead.
- Which Laravel versions does fi/bootstrapitaliabundle support?
- None. The package targets Symfony and Twig, and its composer.json requirements concern PHP and Symfony versions rather than Laravel. Laravel's service provider lifecycle does not load Symfony bundle extension classes. Any claim of Laravel version compatibility should be treated as unsupported.
- What does fi/bootstrapitaliabundle actually provide?
- Based on the overview, it supplies ready-to-use Twig templates, form themes, Bootstrap Italia assets, and configuration for Symfony. The practical deliverable is Bootstrap Italia front-end assets plus Twig markup and form overrides. It is not a Laravel component library and does not publish Blade views, configuration, or migrations. Strip the Twig layer and the remaining value is the upstream design system.
- Is fi/bootstrapitaliabundle maintained and safe for production?
- The upstream repository is archived, with 2 stars and 0 dependents, so there are no security patches, PHP or Symfony version bumps, or accessibility fixes. Bootstrap Italia itself keeps evolving, including the Bootstrap 4 to 5 migration and AGID guideline revisions, and this bundle will be frozen against whichever iteration it pinned. An abandoned Composer package also transitively freezes old front-end dependencies, which is a known CVE accumulation profile. For production, do not adopt it.
- What is the license of fi/bootstrapitaliabundle?
- The license is not confirmed in the provided context, and Italian public-sector repositories vary between EUPL-1.2 and AGPL. AGPL has distribution implications that may not suit your intended distribution model, so check the composer.json license field and the repository LICENSE file before any use. Given the package is archived and unmaintained, this is a due-diligence item rather than a reason to adopt.
- Does fi/bootstrapitaliabundle depend on the Comune di Firenze fifree layout?
- The per fifree layout description signals a dependency on a Comune di Firenze internal layout package. Consuming it outside that context likely pulls in undocumented asset paths, template blocks, and theming variables that are untestable for an external team. It is a context-coupled bundle, not a general-purpose integration. Confirm the composer.json require entries if you need certainty.
- What should I use instead of fi/bootstrapitaliabundle in Laravel?
- Use Bootstrap Italia upstream, installed from npm or the CDN distribution at a current supported version, and wrap its components in your own Blade components such as x-bi-button. That gives you the maintained artifact that carries accessibility fixes, without the abandoned Symfony wrapper. You can read this repository as a reference for markup conventions, but do not depend on it. This is a small in-house component library, not a fork.
- How do I integrate Bootstrap Italia into Laravel Blade templates?
- Install bootstrap-italia from npm or the CDN, include its CSS and JS in your Vite or asset pipeline, and build Blade components for the design system patterns you need. Use this bundle only as a read-only reference for Twig markup and form theme conventions, and rewrite them as Blade rather than bridging Twig. Audit the repository for SCSS overrides and any fifree-specific asset wiring before copying anything. Then test accessibility against AGID and WCAG expectations on the upstream version.