- What is brandymedia/turbine-ui-core used for?
- Turbine UI Core is the foundational Laravel package for BrandyMedia's Turbine UI. It provides reusable Blade components, layouts, and form elements for building consistent interfaces, and it is designed to pair with Tailwind CSS. Developers use it as a lightweight, customizable base for Laravel applications rather than a full admin or auth framework.
- How do I install Turbine UI Core in a Laravel application?
- Install it with composer require brandymedia/turbine-ui-core and let Laravel discover the service provider. Publish the package assets and views with vendor:publish, then make sure Tailwind CSS is configured to scan the published components. Confirm the publish tags and paths in the package docs because v2.1.6 moved Breeze and profile templates into stubs.
- Does Turbine UI Core support Laravel 13?
- Version 2.1.6 adds Laravel 13 support, which suggests the maintainer is tracking current framework releases. Treat that as a compatibility claim until you confirm the minimum PHP version and run a test install in your application. Ask whether the package has CI coverage against Laravel 13 before relying on it for production.
- Can I use Turbine UI Core with Laravel Breeze?
- Yes, Turbine UI Core is designed to layer onto Laravel Breeze rather than replace it. It publishes Blade profile templates and stubs that integrate with Breeze scaffolding, so your application keeps ownership of the generated views. This composable approach works best when your Breeze stack uses Blade rather than Inertia, React, or Vue.
- Which front-end stacks work with Turbine UI Core?
- The package targets Laravel Blade templating with Tailwind CSS, especially Breeze applications that use the Blade stack. It is a poor fit for API-only services, Inertia or React/Vue front ends, and apps that use Jetstream, Fortify-only auth, or a custom auth layer. Confirm your front-end stack before scoping an integration.
- How do I publish Turbine UI Core views and stubs?
- Run php artisan vendor:publish and select the Turbine UI Core provider or tag. In v2.1.6 the Breeze and profile publish templates moved into stubs, so verify the current tag and destination path before publishing. If you already published older templates, compare them with the new stubs instead of blindly re-publishing.
- Why did my view:cache fail after upgrading Turbine UI Core?
- Version 2.1.6 is framed as a fix for production view caching, so earlier published templates may not have been resolvable by php artisan view:cache. After upgrading, run php artisan view:cache as an explicit acceptance check. If it fails, review the published view paths and compare your app's templates with the new stubs.
- Is Turbine UI Core safe for production use?
- The package is a conventional Laravel add-on that registers publishable assets and keeps out of the runtime request path, which is a low-coupling shape. Production risk is concentrated in publish-path changes and stale published views that do not update automatically. Test view caching, re-publish carefully on upgrades, and review profile-handling code for mass assignment, authorisation, and file upload concerns if you use it.
- How do I customize Turbine UI Core components with Tailwind CSS?
- Publish the Blade components into your application and edit the markup and Tailwind utility classes directly. Ensure your tailwind.config.js content paths include the published component directories so the classes are not purged. This keeps the base lightweight and lets you adapt layouts and form elements to your design system.
- What are the alternatives to Turbine UI Core?
- Alternatives include Laravel Breeze's default Blade components, Laravel Jetstream, Blade UI Kit, and building your own Tailwind component library. Turbine UI Core is most compelling when you want a small, publishable Blade component base that pairs with Breeze and Tailwind. If you need a full admin panel or auth suite, evaluate a broader framework instead.