Weave Code
Feature Toggle Bundle Laravel Package
kukulili-labs/feature-toggle-bundle
A Symfony bundle for managing feature toggles in your application. Define flags, check whether features are enabled for users or environments, and roll changes out gradually without redeploying code.
A bundle to manage feature toggles.
Frequently asked questions about Feature Toggle Bundle
- Does kukulili-labs/feature-toggle-bundle work with Laravel?
- It is a Symfony bundle, not a Laravel package. It relies on Symfony bundle conventions, the Symfony dependency injection container, configuration, and Twig helpers, so it will not install into a Laravel application as a drop-in dependency. Using it in Laravel would require a custom adapter or service provider, which turns a cheap Composer require into a bespoke integration project. Confirm compatibility in a timeboxed spike before committing any effort.
- How do I install kukulili-labs/feature-toggle-bundle?
- Installation is through Composer, followed by registering the bundle in your Symfony kernel and defining toggles in configuration. The package is distributed under the MIT license, which removes legal friction but not provenance risk. The repository metadata publishes no release history, versioning scheme, or CI status, so check the composer.json constraints against your target PHP version first.
- Which Laravel and PHP versions does this feature toggle package support?
- No Laravel version support is declared because the package targets Symfony, not Laravel. The metadata does not publish a release history or documented Composer constraints for PHP versions either. Review composer.json in the repository and run a dependency resolution against your target PHP before planning any work.
- Does it support percentage rollouts and user targeting, or only boolean flags?
- The overview describes strategy-based targeting for gradual rollouts and user segmentation, so the intent goes beyond simple on and off switches. However, the exact evaluation semantics such as percentage buckets, segment rules, per-environment state, and scheduled activation are not documented in the available metadata. Confirm whether bucketing is deterministic and sticky per user before relying on it for experiments.
- Where does the bundle store feature toggle state?
- The package defines toggles in configuration and exposes them through a simple service, which points to config-driven state. Whether it also supports database, cache, or remote API storage is not established in the metadata. This matters because toggles are evaluated on hot request paths and inside queued jobs, so the storage and caching model determines whether you add a datastore round trip to every request.
- Can I check feature flags inside Blade templates or queued jobs?
- The bundle ships Twig helpers, not Blade directives, so Laravel views would need a custom wrapper. Toggles are a cross-cutting concern: adoption touches controllers, jobs, views, API middleware, and queue workers. Define a first-party interface such as isEnabled(string $flag, ?User $scope): bool and bind the package behind it so call sites stay framework-agnostic.
- How do I test code that uses this feature toggle bundle?
- The overview advertises a clean, testable API for guarding new or experimental code paths, which implies toggles can be flipped in test setup. In a Laravel application the practical approach is to depend on your own feature flag interface and stub that in tests rather than touching the vendor code. That keeps test suites fast and caps migration cost if the package is abandoned later.
- Is kukulili-labs/feature-toggle-bundle production ready?
- Public signals are thin: roughly three stars, zero dependents, and no visible release history or CI status. Zero dependents is the strongest signal, because no one has publicly taken this dependency, so no one has publicly hit its bugs. MIT removes legal friction but not provenance or maintenance risk, so confirm the copyright holder and maintainer commitment before production use.
- What happens on a cache miss or store outage, does it fail open or closed?
- The available metadata does not document failure behavior, cache TTL, or invalidation strategy. This is a critical question for feature flags because a toggle library that fails open can expose unfinished functionality during an outage. Read the source or ask the maintainer to confirm the default-on versus default-off behavior before shipping.
- What are the alternatives to this Symfony feature toggle bundle for Laravel?
- Laravel Pennant is the first-party feature flag option and integrates with the Laravel container, Blade, and tests out of the box. Hosted services such as LaunchDarkly or Unleash offer targeting, audit trails, and admin surfaces if you need them. A thin in-house FeatureFlag interface with a config or database driver is often the lowest-risk starting point.
Weaver
How can I help you explore Laravel packages today?