Weave Code
Jetstrap Laravel Package
nascent-africa/jetstrap
Jetstrap is a Laravel package that replaces Jetstream's default Tailwind frontend with Bootstrap 5. It scaffolds authentication, profile, password reset, and email verification views, plus team and API support, so you can build responsive Bootstrap-based Laravel apps faster. Install via Composer.
A Laravel 8 package to easily switch TailwindCSS resources generated by Laravel Jetstream and Breeze to Bootstrap 4.
Frequently asked questions about Jetstrap
- What does Jetstrap do for Laravel Jetstream and Breeze?
- Jetstrap is a Laravel 8 package that replaces the TailwindCSS views generated by Laravel Jetstream and Breeze with Bootstrap 4 equivalents. It scaffolds authentication, registration, password reset, email verification, profile updates, API tokens, and team views so Bootstrap-styled Blade files are available after running its Artisan commands. It is a scaffolding and conversion tool, not a general Bootstrap theming layer for your whole application.
- How do I install Jetstrap in a Laravel 8 application?
- Install it with Composer using composer require nascent-africa/jetstrap, then follow the README's Artisan commands to publish the Bootstrap stubs and views. Run it in a disposable branch first so you can review the generated diff before merging. Pin Laravel 8, your Jetstream or Breeze version, and your Node/Webpack toolchain, because the package targets that legacy stack rather than current Laravel releases.
- Does Jetstrap support Laravel 9, Laravel 10, or Laravel 11?
- No. Jetstrap was built for Laravel 8 with the Jetstream and Breeze generation of that era, and its last release was in February 2022. It is not designed for Laravel 9, 10, or 11, Vite, Tailwind 3, or current Jetstream/Breeze versions, so expect dependency conflicts and missing views if you try. For modern Laravel, use it only as a reference implementation for Bootstrap auth and profile views.
- Is Jetstrap Bootstrap 4 or Bootstrap 5?
- The Composer package description states that it switches Tailwind resources to Bootstrap 4, and the technical assessment confirms Bootstrap 4.x expectations. Some third-party blurbs mention Bootstrap 5, so check the CSS and JavaScript assets plus any package.json output in the exact version you install before committing. Mixing Bootstrap 4 markup with Bootstrap 5 JavaScript will break components such as dropdowns and modals.
- Which Jetstream stacks does Jetstrap support: Livewire, Inertia, Vue, or React?
- Jetstrap primarily targets Blade-based views used by Jetstream's Livewire and Inertia stacks, including auth, profile, password reset, email verification, API token, and team screens. React and Vue Jetstream stacks rely on JavaScript components rather than Blade stubs, so the package does not meaningfully convert those. Verify coverage for your exact stack in a time-boxed proof of concept before adopting.
- Will Jetstrap overwrite my customized Jetstream or Breeze views?
- Jetstrap publishes default Bootstrap views, so customized Tailwind views or components at the same paths can be overwritten. Always run it on a clean branch, commit your work first, and inspect the generated diff file by file. If you have custom auth or profile logic, move it into your own views or components after the swap rather than re-running the scaffolding command.
- Does Jetstrap work with Vite and Tailwind 3, or does it need Laravel Mix?
- It targets the Laravel 8 era of Laravel Mix and Webpack with Tailwind 2-era tooling, not Vite or Tailwind 3. Review and adapt the published Bootstrap assets and any package.json snippets if you run a newer build pipeline. Combining a Jetstrap swap with a Mix-to-Vite migration in the same release is risky, so separate those changes.
- What JavaScript dependencies does the generated Bootstrap 4 UI require, such as jQuery and Popper?
- Bootstrap 4 JavaScript components such as dropdowns, modals, tooltips, and collapse typically depend on jQuery and Popper.js, so check the package's asset and package.json output for the exact versions it expects. Confirm those libraries load once, in the correct order, through Mix or your layout. If you want to avoid jQuery entirely, this package is the wrong fit.
- How should I test a Laravel app after swapping to Bootstrap with Jetstrap?
- Cover registration, login, logout, password reset, email verification, profile update, API token management, and teams with feature tests, plus a browser test such as Laravel Dusk for JavaScript-driven components like modals and dropdowns. Run composer audit and npm audit after installing, and pin every version in a compatibility matrix. Test in a disposable branch before rolling the change out to a real application.
- Is Jetstrap still maintained and safe for production, and can I remove it after scaffolding?
- Jetstrap is community-maintained with no releases since February 2022, so treat it as a one-time scaffolder rather than a long-lived dependency. Run it in an isolated branch, inspect and commit the generated Bootstrap views and assets, then remove the Composer package from your runtime dependencies. If you must keep it, fork and pin it internally, assign an owner, and track Laravel and Bootstrap security advisories; the preferred exit is generated-code ownership.
Weaver
How can I help you explore Laravel packages today?