Progressive Bundle Laravel Package

Getting Started

Install the package via Composer:

composer require vendor/package-name

Publish the configuration (if needed) and add the service provider to config/app.php under providers. The new v1.1 feature adds a Symfony Profiler toolbar tag displaying all defined features—no additional setup is required if using the default configuration. To test, trigger a profiler dump (e.g., via php artisan route:list or a debug route) and check the Web Profiler toolbar for the new "Features" tab.

Implementation Patterns

Feature Flag Integration

Use the package’s Feature facade to define and check features:

use Vendor\Package\Facades\Feature;

// Define a feature (e.g., in a service provider boot method)
Feature::define('new-payments-gateway', false);

// Check in middleware/controllers:
if (Feature::enabled('new-payments-gateway')) {
    // Enable new logic
}

Profiler-Driven Workflows

Leverage the new v1.1 Profiler tag to:

1. Debug feature states during development without logging.
2. Validate feature flags across environments by inspecting the toolbar during requests.
3. Share feature configurations with non-technical stakeholders via screenshots of the profiler.

Conditional UI/Logic

Combine with Blade directives for dynamic UI:

@feature('dark-mode')
    <link rel="stylesheet" href="/css/dark.css">
@endfeature

Gotchas and Tips

Profiler Visibility

• The Symfony Profiler tag only appears in development (app.debug=true). Disable it in production by setting:

  'profiler' => [
      'enabled' => env('APP_DEBUG'),
  ]
  

  in the package config.

Feature Persistence

Features are not persisted by default. For runtime persistence (e.g., database-backed flags), extend the package’s FeatureManager:

// config/package.php
'manager' => Vendor\Package\Managers\DatabaseFeatureManager::class,

Toolbar Overhead

The Profiler tag adds minimal overhead (~1ms per request). Disable it in performance-critical paths by:

Feature::disableProfiler(); // Temporarily hide the tag

Deprecation Note

No breaking changes in v1.1, but future versions may move feature storage to a dedicated config table. Monitor the changelog for updates.