Weave Code
Featurit Sdk Symfony Laravel Package
featurit/featurit-sdk-symfony
Symfony SDK for integrating Featurit feature flags into your PHP applications. Manage toggles, target users, and control feature rollout from Symfony services with a simple, configurable client.
Featurit SDK for Symfony integrates the Featurit feature flagging service into Symfony applications, letting you toggle features and run A/B tests without redeploying code. It provides a clean Symfony bundle that resolves flag values at runtime based on your Featurit account, environment, and user context.
- Simple Symfony bundle registration and configuration
- Runtime feature flag evaluation with user/targeting context
- Supports percentage rollouts and A/B testing
- Configurable caching to reduce remote calls
- PSR-friendly, framework-native service integration
Frequently asked questions about Featurit Sdk Symfony
- Is featurit/featurit-sdk-symfony a Laravel package?
- No. It is a Symfony bundle, and Laravel does not use the Symfony bundle, dependency injection, or HttpKernel model. Bundle auto-registration, services.yaml wiring, tagged services, and event subscribers will not load in a Laravel app. Treat it as an adjacent-runtime SDK and evaluate FeaturIT's framework-agnostic PHP client or REST API for Laravel.
- How do I install and configure FeaturIT in a Laravel application?
- Composer can install the package, but the Symfony bundle wiring will not auto-register in Laravel. You would need an application-owned config/featurit.php, a service provider, a FeatureFlags contract bound to the SDK client, and optional Blade and middleware integration. Before committing, run composer why-not against your Laravel lockfile and confirm the PHP version matrix.
- Does this SDK support Laravel 11 and Laravel 12?
- The package targets Symfony and does not declare Laravel support. Laravel 11 or 12 on PHP 8.2+ may be feasible only if FeaturIT ships a framework-agnostic core client that the Symfony bundle merely decorates. Test it in a throwaway non-production app before adding it to a real application.
- Can I use FeaturIT feature flags in Blade templates or Twig?
- The package documents Twig integration for Symfony, which does not help in Laravel because Laravel uses Blade. Add a Blade directive or view composer that calls your own FeatureFlags service instead of referencing the SDK directly. Keeping templates behind an application-owned abstraction also makes the vendor swappable later.
- Does the FeaturIT SDK cache flag evaluations, or does it call the API every time?
- Caching behavior is not clear from the package overview and must be validated before production use. If each evaluation hits the FeaturIT API, the SDK is unusable in a hot path. Add a caching decorator using Redis or an in-process array with a TTL and background refresh, then measure evaluation latency with and without cache.
- What happens when FeaturIT is unreachable or returns an error?
- The failure behavior is not specified in the available context, so ask the vendor whether it fails open, fails closed, uses last-known-good values, or returns coded defaults. Make the fallback configurable per flag and ship a config driver with static defaults before any remote dependency exists. This ensures critical paths keep working during an outage.
- Is it safe to send user attributes to FeaturIT for targeting?
- FeaturIT targeting requires sending user attributes to a third party, so review PII scope and data residency before any customer-facing flag goes live. Minimize attributes, hash identifiers where possible, and document what is transmitted. Gate adoption on security and privacy approval rather than treating targeting as a purely technical decision.
- Does this package work with Laravel Octane and long-lived workers?
- There is no native Laravel or Octane support in a Symfony bundle. Under Octane, validate singleton client state, configuration reload behavior, and cache lifetime across requests. Prefer request-scoped user context and a stateless wrapper around the FeaturIT client, then test explicitly under Octane before rollout.
- What is the best alternative to this Symfony bundle for Laravel?
- Look for a framework-agnostic FeaturIT PHP SDK, the FeaturIT REST API, or an official Laravel package before adapting this bundle. Wrap whichever client you choose behind an application-owned FeatureFlags interface with featurit, config, and null drivers. That keeps controllers, jobs, and Blade templates independent of the vendor and makes tests straightforward.
- Is featurit/featurit-sdk-symfony maintained and production-ready?
- Adoption signals are thin: around 4 stars, 0 dependents, and a single recent release in January 2025. It is likely vendor-maintained, so bus factor and release cadence depend on FeaturIT's commercial health. Treat it as a timeboxed spike, not a procurement, and gate production use on a support contract, SLA, semver discipline, and a security disclosure process.
Weaver
How can I help you explore Laravel packages today?