Weave Code
Feature Bundle Laravel Package
ruwork/feature-bundle
Symfony bundle for managing feature flags and toggles. Define features in configuration, inject them as services, and enable or disable application behavior without redeploying, with simple checks for gradual rollout and conditional code paths.
ruwork/feature-bundle is a Symfony bundle for managing feature flags in your application, letting you enable or disable functionality without redeploying code. Define features once and toggle them per environment, keeping unfinished work safely behind flags.
- Simple feature flag registration and configuration
- Environment-aware toggling for dev, staging, and production
- Lightweight integration with the Symfony service container
- Easy checks in controllers, services, and Twig templates
- Minimal setup with sensible defaults
Frequently asked questions about Feature Bundle
- Is ruwork/feature-bundle compatible with Laravel?
- No. ruwork/feature-bundle is a Symfony bundle, not a Laravel package, so it does not follow Laravel service provider, facade, container, or middleware conventions. Laravel applications should treat it as unsupported and use native configuration or Laravel Pennant instead.
- Can I install ruwork/feature-bundle in a Laravel 10 or 11 app?
- Composer may allow installation, but there is effectively no Laravel integration. The package is archived and likely targets PHP 7.x and older Symfony versions, creating friction with modern PHP 8.x and Laravel 10 or 11. It should not be adopted for new Laravel work.
- What is ruwork/feature-bundle used for?
- It is a lightweight Symfony/PHP feature flag bundle for defining and toggling features through configuration and checking them in services or templates. That supports gradual rollouts, A/B testing, and safer deployment of new functionality. However, the project is archived and not suitable for modern Laravel stacks.
- Is ruwork/feature-bundle still maintained?
- No. The repository is archived, has 0 stars and 0 dependents, and has had no releases since 2018-04-29. There are no active maintainers or upstream support, so any use would require forking and internal ownership.
- What are the best alternatives to ruwork/feature-bundle for Laravel feature flags?
- Laravel Pennant is the natural first choice for Laravel applications. For broader needs, consider Unleash, Flagsmith, OpenFeature-style abstractions, or a simple database or config-backed toggle. Evaluate based on rollout, audit, and distributed evaluation requirements.
- Does ruwork/feature-bundle support PHP 8.2 or 8.3?
- That is unlikely. The package predates modern PHP versions and its Composer constraints are expected to target PHP 7.x-era environments and older Symfony releases. Treat PHP 8.2 and 8.3 support as unproven unless a fork with tests demonstrates compatibility.
- How do I migrate from ruwork/feature-bundle to Laravel Pennant?
- Inventory every flag, annotation, default, and environment override before changing code. Map those flags to Pennant features, run dual-read or shadow evaluation where possible, then remove the bundle. There is no supported migration path from the package itself, so plan an incremental cutover.
- Is ruwork/feature-bundle safe for production use?
- It carries high technical risk because it is unmaintained, has no upstream security response, and shows no evidence of active CI or compatibility testing. Feature flags are control-plane components, so failures can expose disabled features or hide enabled ones. Production use would require a fork, security review, fail-safe defaults, and an exit plan.
- Can I use ruwork/feature-bundle in a legacy Symfony application?
- Only with caution. A legacy Symfony app could consider it after forking, auditing PHP and Symfony constraints, and isolating it behind an internal feature-flag interface. Do not embed it directly in application code, and plan to migrate to a maintained flag system.
- Why should Laravel developers avoid ruwork/feature-bundle?
- It is a Symfony bundle with no Laravel conventions, no active maintenance, and no upstream support. Adopting it creates long-term ownership burden for a capability that Laravel already addresses with configuration and Pennant. For new Laravel work, do not adopt it.
Weaver
How can I help you explore Laravel packages today?