- What is manusiakemos/tall-stack-kit?
- It is a Laravel starter kit for building applications with the TALL stack: Tailwind CSS, Alpine.js, Laravel, and Livewire. It bundles common scaffolding and UI components so a new project can start with a modern, reactive PHP stack instead of assembling those pieces manually.
- How do I install the TALL stack starter kit with Composer?
- Install it like any Composer package with composer require manusiakemos/tall-stack-kit, then follow the package's setup steps for scaffolding and publishing assets or views. Because it is a starter kit, the intended path is typically a fresh Laravel application rather than bolting it onto an existing, heavily customised project. Check the README for the exact publish and install commands before running it.
- Which Laravel and PHP versions does this package support?
- The release notes for 1.2.25 do not state a support window, so verify the Laravel and PHP constraints in the package's composer.json rather than assuming. Confirm that your pinned Laravel and PHP versions are included before upgrading. This matters most if your application is on an older but still supported Laravel release.
- How do I add custom tabs and breadcrumbs using slots?
- Version 1.2.25 adds slot support to custom tabs and custom breadcrumbs, letting you inject arbitrary Blade markup into those navigation surfaces without forking the package views. In practice you pass a slot or view name when declaring the tab or breadcrumb entry. Check whether the slot is available for both the tab label and body, and whether a breadcrumb slot replaces the crumb link or composes alongside it.
- Is upgrading to 1.2.25 a breaking change for existing Laravel apps?
- The change is additive: slots are a new extension point for tabs and breadcrumbs, and existing instalments should not be forced to migrate. Bump the constraint to ^1.2.25, update in a branch, rebuild compiled views, and visually diff the affected navigation. Because a feature shipped in a patch release suggests a fast-moving release cadence, pinning the version is reasonable.
- Do the new tab and breadcrumb slots work with cached Blade views?
- New slot rendering paths can behave differently under view:cache, so test with cached views before deploying. Run php artisan view:clear and php artisan view:cache in staging as part of your upgrade check. If something renders incorrectly only when views are cached, that is the first thing to investigate.
- Are slot contents escaped, and is there an XSS risk?
- Custom slots imply raw HTML injection by design, so treat slot content as trusted, developer-supplied markup rather than user input. Confirm that variable interpolation inside slots still uses Blade's {{ }} escaping semantics and that no user-controlled data is passed in unescaped. If you need to render user data inside a slot, escape or sanitise it before it reaches the slot.
- Will published view overrides hide the new slot feature?
- Likely yes. If your application currently customises tabs or breadcrumbs by publishing and overriding the package views, those overrides will shadow the new slot-based extension points. Treat retiring them in favour of slots as an optional cleanup rather than an obligation, because it reduces long-term drift between your overrides and upstream changes.
- Does the kit work with Livewire and other Laravel front-end stacks?
- The kit is built around Livewire and the TALL stack, so that is its native path. The slot feature is confined to the presentation layer, so it composes cleanly with Blade-based stacks, including Inertia applications that use a Blade shell. It does not imply any additional runtime dependency, queue worker, or infrastructure change.
- How does it compare with Laravel Breeze or Jetstream?
- Breeze and Jetstream are official Laravel starter kits with their own opinions about authentication and front-end scaffolding, while this package is a community TALL stack kit focused on Tailwind, Alpine, and Livewire scaffolding with UI components. Evaluate it against your existing stack, the UI components you actually need, and the package's maintenance cadence. If you already use an official starter kit, adopting this one is a larger architectural decision than a simple Composer require.