- What is realrashid/plan-craft used for in Laravel?
- Plan Craft is a Laravel package for defining and managing subscription plans, features, and usage limits in code. You can attach plans to any model, gate features by plan, and track subscriptions through a flexible API. It is aimed at SaaS applications that want code-driven plan management rather than conventional database-only storage.
- How do I install realrashid/plan-craft?
- Install it with Composer using composer require realrashid/plan-craft. For the v2 line, plan for Laravel 13 and PHP 8.3+ before installing. Check the package README for any config publishing, migrations, or model setup steps.
- Does Plan Craft support Laravel 12 or PHP 8.2?
- The v2.0.0 release positions Plan Craft for Laravel 13 and PHP 8.3+, so do not assume compatibility with Laravel 12 or PHP 8.2. If your app is still on an older platform, pin the latest v1.x release and confirm the Composer constraints before upgrading. Treat the package upgrade as coupled to your PHP and Laravel upgrade.
- Does Plan Craft handle subscription billing, or do I need Laravel Cashier?
- Plan Craft focuses on plans, features, usage limits, and subscriptions; it is not described as a payment or billing processor. If you need Stripe or Paddle billing, Laravel Cashier is the usual companion, while Plan Craft handles feature gating and plan state. Confirm the README for any billing integrations before choosing it as a Cashier replacement.
- How do I attach a plan to a model with Plan Craft?
- Plan Craft is designed to attach plans to any Eloquent model and track subscriptions through its API. The exact trait, relationship, or model setup should be taken from the README for your installed version. This lets you keep plan state on users, teams, or other billable entities.
- How do I gate features by plan in Plan Craft?
- Use Plan Craft's feature-gating API to check whether a model's current plan includes a feature or has remaining capacity. The package is built around gating features by plan, so keep the checks close to authorization or policy logic. Refer to the README for the exact method names in v2.0.0.
- How does Plan Craft track usage limits?
- Plans can define usage limits, and Plan Craft tracks subscriptions so you can enforce those limits per model. A typical flow checks the limit before an action and records usage through the package API. Verify the exact increment and reset methods in the README, especially after a major upgrade.
- Is Plan Craft v2.0.0 a breaking change from v1.x?
- Treat v2.0.0 as a potentially breaking major release until the changelog and upgrade guide confirm the API impact. The clearest change is the new platform baseline of Laravel 13 and PHP 8.3+, but major versions can also include behavior changes. Test plan attachment, feature gating, and usage tracking in a branch before rolling it out.
- Are Testbench v11 and Pest v4 required in production for Plan Craft?
- Testbench v11 and Pest v4 are typically development and CI dependencies for the package, not production runtime requirements. They should not affect your application unless they are required transitively or you run the package's own test suite. Check the published composer.json constraints if you need certainty.
- How should I test Plan Craft after upgrading in a Laravel app?
- Run your application test suite after upgrading, with extra coverage for plan attachment, feature gates, and usage-limit enforcement. If you use Pest, align your test tooling with the package's supported version, and update your CI matrix for PHP 8.3 and Laravel 13. For package contribution, match Testbench v11 and Pest v4 in the package pipeline.