Weave Code
Pulsar Laravel Package
jadu/pulsar
Pulsar is a Laravel package from Jadu that provides a lightweight, configurable toolkit for PHP applications. It focuses on simple setup and Laravel-friendly integration, helping developers add reusable components and common workflows without extra overhead.
The User Experience and Interface framework by Jadu.
Frequently asked questions about Pulsar
- What is jadu/pulsar used for in Laravel?
- Pulsar is a lightweight feature flag package for Laravel from Jadu. It lets you define features and evaluate them at runtime so you can ship changes behind safe defaults, run gradual rollouts, and target specific users without scattering conditionals through application code.
- How do I install jadu/pulsar in a Laravel application?
- Install it with Composer using composer require jadu/pulsar. Pulsar integrates with Laravel's configuration and service container, so package discovery and setup follow familiar Laravel conventions. Check the README for any config publishing or environment-specific steps before rolling it out.
- How do I define a feature flag with Pulsar?
- You can define features in Pulsar's configuration or directly in code, then evaluate them through a fluent API. That keeps flag definitions centralized and makes runtime checks readable. The config-driven approach also lets you change defaults per environment without code changes.
- How do I check a feature flag in a Blade template with Pulsar?
- Pulsar provides a Blade directive so you can conditionally render markup based on a feature flag. Use it to hide unfinished UI or expose new flows to a subset of users. Keep the evaluation logic in PHP where possible and use Blade mainly for presentation-level toggles.
- Can Pulsar target specific users or segments?
- Yes. Pulsar supports targeting users and segments with custom rules, so you can enable a feature for specific accounts, cohorts, or other criteria. You define the rule logic and Pulsar evaluates it at runtime. This is useful for beta programs and gradual rollouts.
- How do I protect routes with Pulsar feature flags?
- Pulsar includes middleware for gating routes behind a feature flag. Add the middleware to the route or route group and requests are checked before the controller runs. This keeps feature gating out of controllers and consistent across endpoints.
- How do I override feature flags in Laravel tests with Pulsar?
- Pulsar is designed to let you override flags easily in tests, so you can assert both enabled and disabled behavior without hitting real targeting rules. Set the flag state in the test setup and exercise the code path. That keeps feature-flagged tests deterministic.
- Which Laravel and PHP versions does jadu/pulsar support?
- The provided package details do not include a supported Laravel and PHP version matrix. Check the package's composer.json and README for the required PHP version, Laravel constraints, and any deprecation policy. Confirm compatibility with your application's Laravel version before adopting it.
- Is jadu/pulsar safe to use in production?
- Treat Pulsar as a small, single-vendor package and do your own diligence. The project has a low community footprint, and the repository is listed as unknown, so review commit activity, issue responsiveness, and release history before production use. Its MIT license does allow you to fork and maintain it internally if needed.
- What are alternatives to jadu/pulsar for feature flags in Laravel?
- Laravel Pennant is the first-party feature flag option and is a natural comparison for many teams. Other choices include hosted services such as LaunchDarkly, Flagsmith, or Unleash. Pulsar may suit teams that want a lightweight, config-driven package with a fluent API and Blade integration.
Weaver
How can I help you explore Laravel packages today?