Weave Code
Jetstreampro Laravel Package
jetstreamlabs/jetstreampro
JetstreamPro is a Laravel package that extends Laravel Jetstream with extra tooling for authentication, teams, and user management, aiming to streamline common SaaS scaffolding. Adoption is limited and documentation is sparse, so evaluate carefully before use.
Laravel Jetstream Professional. Includes Vite, Unplugin, Semantic-Release, Github-Actions and more.
Frequently asked questions about Jetstreampro
- What is jetstreamlabs/jetstreampro used for?
- It is a Laravel application scaffold layered on Laravel Jetstream, aimed at speeding up SaaS front ends with auth, teams, profile management, Inertia/Vue, and Tailwind UI. It also bundles tooling such as Vite, Unplugin, Semantic Release, and GitHub Actions. Treat it as a starter kit you fork and own, not a runtime library you upgrade in place.
- How do I install jetstreamlabs/jetstreampro in a Laravel app?
- It is Composer-installable, but integration is scaffold-once rather than a normal dependency. You install it into a greenfield Laravel 9 and Jetstream 2.16 baseline, then publish and own config, migrations, Vue/Inertia pages, Tailwind, and Vite files. Check the repository and license terms before adopting because documentation is sparse.
- Does jetstreampro support Laravel 10 or Laravel 11?
- The evaluated release only bumps laravel/framework from 9.50.0 to 9.50.2 and laravel/jetstream from 2.15.0 to 2.16.0. It gives no signal of Laravel 10 or Laravel 11 readiness, and no vendor-published support matrix is described. Treat Laravel 9 as the safe assumption until upstream states otherwise.
- Is jetstreamlabs/jetstreampro a library or a starter kit?
- It is an application scaffold/starter kit layered on Laravel Jetstream, not a package consumed at runtime inside an existing domain model. Its value is accelerating greenfield Laravel SaaS front ends with auth, teams, and profile management. That means you adopt a template and then maintain your fork rather than upgrading a versioned dependency in place.
- What changed in jetstreampro v3.5.13?
- The release is maintenance-only: dependency churn, formatting, and CI hygiene, with no product-facing features, fixes, or breaking-change markers. Notable dev-toolchain changes include PHPUnit 9.5.28 to 10.0.3, plus Tailwind, unplugin, webpack, and axios bumps. It does not raise the Laravel framework ceiling or signal PHP 8.3 validation.
- Should I worry about PHPUnit 10 in jetstreampro?
- PHPUnit moves from 9.5.28 to 10.0.3 as a dev dependency, so production risk is minimal. However, any test scaffolding, CI config, or example test suite copied from the package inherits a breaking test harness with annotation-to-attribute migration and phpunit.xml schema changes. Plan for PHP 8.1+ if you reuse that tooling.
- How do I maintain a Laravel Jetstream scaffold after forking it?
- The package ships published assets such as config, migrations, Vue/Inertia pages, Tailwind, and Vite config, so integration means scaffold once and own the code. Subsequent releases are advisory input to a manual diff, not automatic upgrades. Expect formatting churn and frontend toolchain drift to create spurious diffs if you patch or vendor the package.
- What are the risks of using jetstreampro in production?
- The main risks are sparse documentation, limited adoption, and an unclear support matrix for Laravel and PHP versions. The release history is maintenance-heavy, and patch releases may not guarantee semver stability for scaffolded files. Evaluate license terms, update windows, and whether your team can own the fork long term.
- Does jetstreampro work with Vite and Tailwind?
- Yes, the package includes Vite as the primary build path and Tailwind config, with residual webpack config still in-tree. The evaluated release bumps Tailwind from 3.2.4 to 3.3.2 and unplugin-auto-import and unplugin-vue-components. Those bumps rarely break a scaffolded app but can break customized vite.config.js or webpack.mix files.
- What alternatives should I consider to jetstreampro?
- Consider stock Laravel Jetstream or Laravel Breeze if you want a well-documented, community-maintained starting point. JetstreamPro adds Vite, Unplugin, Semantic Release, and GitHub Actions, but its limited adoption and sparse docs make it a careful evaluation. Compare support matrices, license terms, and long-term maintenance before choosing.
Weaver
How can I help you explore Laravel packages today?