Weave Code
Tomato Breeze Laravel Package
tomatophp/tomato-breeze
Laravel Breeze integration for TomatoPHP that adds ready-made authentication scaffolding—login, registration, password reset, email verification, and profile management—styled for the Tomato admin panel. Skip hand-written auth views and controllers and ship secure, session-based login in minutes.
Tomato Breeze brings Laravel's Breeze authentication scaffolding into the TomatoPHP admin ecosystem, giving you ready-made login, registration, password-reset, and profile flows that match your panel's look and feel. It wires Breeze's routes and controllers into Tomato's structure so you can ship secure authentication instead of building it from scratch.
- Drop-in Breeze auth routes and controllers for Tomato panels
- Themed Blade views consistent with the Tomato UI
- Profile management for name, email, and password updates
- Simple publish/config setup for easy customization
- Plays nicely with existing TomatoPHP packages
Frequently asked questions about Tomato Breeze
- How do I install tomatophp/tomato-breeze in a Laravel application?
- Install it with Composer, then publish the package's config, routes, views, and assets so the auth scaffolding is copied into your application. Because this is a scaffold rather than a runtime library, the published files become first-party code you own and edit. Run the spike on a throwaway Laravel 10 project first, load /login and /register, then toggle dark mode and set dir="rtl" on the html element to confirm the layout holds before touching a real app.
- Which Laravel and PHP versions does tomato-breeze support?
- The last release was April 2023, which predates Laravel 11's slimmed skeleton and Breeze's own restructure, so assume Laravel 9 or 10, PHP 8.1 or 8.2, Splade 1.x, and Tailwind 3. There is no published Laravel 11 or 12 support, so treat those targets as a port rather than an install. Budget roughly three to five engineer-days for the port, and if it exceeds about five days, take only the RTL and dark mode Tailwind layer onto stock Breeze instead.
- Does tomato-breeze require Splade?
- Yes. Tomato Breeze is effectively a commitment to Splade, the Blade-rendered Vue 3 stack that avoids Inertia and Livewire. That stack decision can happen by stealth if you install the package without agreeing on it explicitly. If Splade is not already your frontend standard, the RTL and dark mode payoff gets buried under a stack migration nobody budgeted for.
- Can I use tomato-breeze alongside Filament or tomato-admin?
- You should not. Running this alongside tomato-admin or Filament creates an architectural collision: two authentication front ends, two theming systems, two upgrade tracks, and a confused web.php. Decide which paradigm owns authentication for the application before the second one lands. The package fits best inside or adjacent to the TomatoPHP ecosystem where admin and UI conventions already match sibling packages.
- Can I install laravel/breeze and tomatophp/tomato-breeze together?
- No. Co-installing with first-party laravel/breeze gives you duplicate routes, conflicting views, and two separate upgrade paths for the same surface. Pick one scaffolding source and remove the other before building product features on top of it. If you adopt Tomato Breeze, commit the generated scaffold and then composer remove the package so you keep the code without the runtime dependency.
- Does tomato-breeze support RTL layouts and dark mode?
- Yes, and first-class RTL and dark mode out of the box is the strongest reason to consider this package at all. Laravel ships Breeze scaffolding for free, so the differentiator is the themed Tomato UI layer with RTL support. Two things to verify in the spike: Tailwind's content globs must include Splade's vendor Blade views or purged classes make the UI look almost right, and the dark class must be applied before paint or the theme flashes white on load.
- How do I customize the login, registration, and profile views in tomato-breeze?
- Publish the package assets and views, then edit the Blade files directly since they live in your application as first-party code. Update your Tailwind content configuration to include the vendor view paths if any templates still render from the package. The recommended pattern is to commit the entire generated scaffold, tag your fork, and drop the Composer dependency so your customizations are not overwritten.
- Is tomato-breeze safe to use for authentication in production?
- This is a 2023-vintage fork of Breeze, and authentication is the surface where stale templates are least acceptable. Before shipping, explicitly diff the password reset flow, signed email verification URLs, and session regeneration logic against current upstream Breeze. Also confirm APP_URL matches your deployed host, because a mismatch breaks signed email links with a generic 403 that reads like an application bug. It is a reasonable fit for an internal back-office, admin, MVP, or demo surface, and needs a security review before it fronts a customer-facing, externally audited login.
- Is tomatophp/tomato-breeze actively maintained?
- The package has zero stars, zero dependents, and its last release was 2023-04-06, so treat it as unmaintained upstream. Because it is a scaffold rather than a library, there is no composer update path to upstream security fixes anyway. The operational answer is to vendor it: commit the generated scaffold with the upstream commit SHA in the message, remove the Composer dependency, tag your own fork, and name an owner for the auth screens from day one.
- What are the alternatives to tomato-breeze for Laravel authentication?
- The two realistic options are stock Laravel Breeze with only the RTL and dark mode Tailwind layer ported over, or Filament's built-in authentication if Filament owns your panel. If RTL is only an aspirational localization-phase requirement rather than a v1 need, the strongest reason to choose this package disappears and stock Breeze wins. Decide which paradigm owns authentication first, then pick the scaffolding that matches it.
Weaver
How can I help you explore Laravel packages today?