Weave Code
Jetstream Laravel Package
laravel-afterburner/jetstream
Laravel Afterburner for Jetstream extends Laravel Jetstream's authentication, profile, and team scaffolding with opinionated enhancements and reusable tooling, helping you build account and admin features faster with less boilerplate.
Laravel Afterburner Jetstream supercharges your Laravel Jetstream application with advanced authentication, team management, and UI enhancements. It delivers a curated set of ready-to-use components and utilities that accelerate development while preserving the elegance of the Jetstream stack.
- Enhanced team permissions with granular role management
- Pre-built Livewire components for common UI patterns
- API token abilities with scoped access control
- Customizable dashboard widgets for quick insights
- Seamless integration with existing Jetstream installations
Frequently asked questions about Jetstream
- What is laravel-afterburner/jetstream and what does it add to a Laravel app?
- It is a Composer package that integrates Jetstream features into the Laravel Afterburner stack. It adds authentication, team support, profile management, and frontend scaffolding. It is described as a self-contained Jetstream successor with custom roles and permissions plus audit logging.
- How do I install laravel-afterburner/jetstream in a Laravel application?
- It is expected to be Composer-installable like typical Laravel packages, with a service provider and publishable config or assets. The exact install command is not in the provided overview, so check the repository README for the Composer require line and publish steps. Test on a throwaway branch first because scaffolding packages can overwrite or conflict with published Jetstream files.
- Which Laravel and PHP versions does laravel-afterburner/jetstream support?
- The assessment assumes Laravel 10/11+ and PHP 8.2+ as a target stack, but the package's declared constraints must be confirmed. A 1.0.0 tag should declare a minimum Laravel and PHP matrix, and that was not available in the release note. Check composer.json and the changelog before adopting.
- Does laravel-afterburner/jetstream use Livewire or Inertia with React or Vue?
- The provided overview does not confirm the front-end commitment. Jetstream traditionally supports Livewire or Inertia with React or Vue, and this package is described as Jetstream integration, so it likely inherits one of those stacks. Verify before adoption because scaffolding choices are hard to swap later.
- How does team support work in laravel-afterburner/jetstream?
- It is described as adding team support as part of the Jetstream feature set. That typically includes team creation, membership, and team-scoped permissions, but the exact implementation is not detailed here. Review the docs and test team-membership flows carefully because they are a common source of regressions.
- Can I use custom roles and permissions with this package?
- Yes, custom roles and permissions are listed among the features in the overview. Because roles and permissions sit next to auth and team logic, treat upgrades as security-relevant. Confirm how roles are persisted and whether they integrate with Laravel gates and policies.
- Does laravel-afterburner/jetstream include audit logging?
- Audit logging is mentioned in the overview as part of the template. The scope, storage, and retention are not described in the provided context. Check whether it logs auth events, team changes, and permission updates, and whether it is enabled by default.
- Is laravel-afterburner/jetstream production-ready?
- It is described as production-ready, but the v1.0.0 release note provides only a changelog URL and commit range. That means stability and breaking-change policy are unconfirmed. Run it in a representative app and review the tag diff before relying on it in production.
- What are the risks of adopting a 1.0.0 scaffolding package like this?
- The main risks are information risk from thin release notes, scaffolding coupling if you have customized Jetstream files, and a small support surface. Security adjacency is also relevant because auth, 2FA, API tokens, and team permissions are in scope. Runtime risk is low because it is pure PHP.
- How does laravel-afterburner/jetstream compare to Laravel Jetstream?
- It is positioned as a self-contained Jetstream successor within the Afterburner stack, adding teams, custom roles and permissions, and audit logging. Standard Jetstream provides auth, teams, API tokens, and front-end scaffolding but not necessarily those extras. For an existing app with customized Jetstream scaffolding, migration should be treated as a project rather than a dependency add.
Weaver
How can I help you explore Laravel packages today?