- How do I install nasirkhan/laravel-cube in a Laravel application?
- Install it with Composer using composer require nasirkhan/laravel-cube. The package service provider is auto-registered and its components are exposed under the x-cube:: namespace, so you can start using tags like <x-cube::button> right away. If you are on Tailwind, add the package CSS import to your stylesheet so the utility classes used by the components are detected during build. Bootstrap projects are largely install-and-use, though interactive components may need JavaScript initialization.
- Does Laravel Cube really work with both Tailwind CSS and Bootstrap 5?
- Yes, dual framework support is the core feature: the same Blade component API renders either Tailwind (Flowbite) or Bootstrap 5 markup. You can switch the framework globally or override it per component, which helps teams standardize UI while keeping their CSS framework of choice. Keep in mind that Tailwind-first features such as dark mode styling are most polished on the Tailwind side, and Bootstrap-only projects may need manual JavaScript setup for interactive elements.
- Which Laravel and PHP versions does Laravel Cube support?
- The README does not pin an explicit Laravel or PHP version, so the authoritative source is the require block in the package composer.json and the constraints shown on Packagist. Check those before installing into an older or very new Laravel app. Because the package moved from v2.6.0 to v4.3.0 quickly, also review the changelog for any framework or dependency requirement changes.
- Is Laravel Cube compatible with Livewire?
- Yes, the package is documented as Livewire 3/4 compatible and is designed for modern hybrid Blade plus Livewire apps. Reactive forms, validation states, and image upload previews are the areas most worth testing in your own application. When mixing Cube components with existing Livewire components, verify that event handling, loading states, and validation messages do not collide. Also confirm the Livewire version your app uses sits inside the range the package currently allows.
- Does Laravel Cube include dark mode support?
- Yes, built-in dark mode is available for the Tailwind-based components, so you can toggle themes without rewriting markup. Bootstrap projects should rely on Bootstrap 5's own color modes and verify each component visually. If you override styles or publish views, re-check dark mode classes after upgrades so custom overrides do not break theming.
- How do I customize or override Laravel Cube component styles?
- The views are publishable, so you can run the package's vendor:publish command and edit the Blade templates locally, or override styles with your own CSS. Publishing gives full control but also means you own those files, so track them and diff against upstream after each upgrade. For smaller tweaks, prefer passing classes or attributes through the component instead of forking the view.
- Is the image upload component safe to use in production?
- It can be, but image uploads add real surface area: MIME type validation, file size limits, storage disk selection, public versus private visibility, and cleanup of orphaned files all need deliberate configuration. Pair the component with Laravel validation rules and a scoped storage disk rather than trusting client-side checks. If you use it with Livewire, test temporary upload behavior, previews, and failure states. If you already run a media library, make sure Cube uploads follow the same storage conventions.
- What is the x-cube::backend.section-show-table component used for?
- It is a backend-oriented Blade component for presenting section and table layouts, documented as of v4.3.0. It is a presentation helper, not a full admin panel, so pagination strategy, authorization checks, empty states, large dataset performance, and responsive behavior remain your responsibility. Confirm whether your table is server-rendered or Livewire-driven before adopting it, since the data shape expectations differ.
- How does Laravel Cube compare to Filament, Nova, or Jetstream?
- Laravel Cube is a reusable Blade UI component library, not an admin panel, authentication suite, or media library. Filament and Nova give you full panel scaffolding with resources, authorization, and CRUD; Jetstream covers auth and team scaffolding. Cube fits teams that want consistent primitives and form components inside their own Blade or Livewire screens. Its newer backend table components can overlap with admin panel patterns, so define a clear boundary between Cube for presentation and a panel package for full admin workflows.
- Is Laravel Cube actively maintained and safe to adopt long term?
- Community signals are still thin, with low adoption and few dependents, so treat long-term maintenance as a real risk and pin the version you validate. The jump from v2.6.0 to v4.3.0 is significant, and while the v4.3.0 notes are additive, you should audit the full changelog for breaking changes before upgrading. Also review transitive dependencies such as themesberg/flowbite-blade-icons. A reasonable approach is to wrap Cube components in your own thin layer so you can swap implementations later if needed.