Laravel Jetstream: Scaling Your Application with Advanced Starter Kits

Prerequisites and Installation

To get started, you should be comfortable with the PHP ecosystem and the basic Laravel directory structure. You can initiate a project using the Laravel installer by selecting Jetstream as your starter kit. During installation, you must choose between two frontend stacks: Livewire with Blade or Inertia.js with Vue.js.

Key Libraries & Tools

• Laravel Sanctum: Powers the API token system, allowing users to issue scoped permissions for third-party integrations.
• Livewire: A framework for building reactive interfaces using only PHP.
• Inertia.js: Bridges the gap between server-side routing and modern single-page applications.
• Tailwind CSS: Handles the utility-first styling for the entire dashboard and profile views.

Customizing the Logic with Action Classes

Jetstream utilizes "Action" classes to handle core logic, found in app/Actions/Jetstream. This pattern keeps your controllers clean and your logic reusable.

// Example: Configuring permissions in JetstreamServiceProvider
Jetstream::role('admin', 'Admin', [
    'create', 
    'read', 
    'update', 
    'delete',
])->description('Administrator users can perform any action.');

You can modify these classes to inject custom validation or business rules directly into the user registration or team creation flows. For UI changes, navigate to resources/views (for Livewire) to edit the dashboard components or the welcome screen.

Syntax Notes & Best Practices

Jetstream leans heavily on Service Providers for configuration. Use the JetstreamServiceProvider to define user roles and granular permissions. One notable pattern is the use of the features array in config/jetstream.php. Toggling a boolean here can instantly enable Two-Factor Authentication (2FA) or profile photo uploads across your entire app.

Tips & Gotchas

Avoid treating Jetstream as a package you periodically update. Once installed, the code lives in your application's app and resources directories. It belongs to you. If you need to change the behavior of the registration process, modify the CreateNewUser action directly rather than trying to extend it. Always remember to run your migrations after enabling team support, as it requires specific database tables to track memberships.