Weave Code
Ui Laravel Package
beartropy/ui
Beartropy UI is a TALL stack component library for Laravel and Livewire with 40+ Tailwind-powered components, including modals, dropdowns, date pickers, a command palette, and dark mode support.
Beartropy UI is a comprehensive component library built for the TALL stack (Tailwind CSS, Alpine.js, Laravel, Livewire). It ships with 40+ ready-to-use components — from buttons, inputs, and modals to advanced elements like command palettes, date/time pickers, and file dropzones — so you can assemble polished interfaces without rebuilding the basics.
- 40+ components covering forms, overlays, layouts, and navigation
- TALL stack optimized for seamless Tailwind, Alpine, and Livewire integration
- Built-in light/dark theming via the
ToggleThemecomponent - AI assistant support with Claude Code skills and Cursor rules
- Developer friendly and easy to drop into existing Laravel apps
Frequently asked questions about Ui
- What is Beartropy UI and which stack does it support?
- Beartropy UI is a component library built specifically for the TALL stack — Tailwind CSS, Alpine.js, Laravel and Livewire — shipping 40+ Blade components such as buttons, inputs, modals, dropdowns, date and time pickers, a command palette, a file dropzone and a chat input. Components are class-based Blade views extending a BeartropyComponent base, rendering through resources/views with a preset layer that maps color names to Tailwind class strings, and interactivity is delegated to Alpine.data modules. It fits Livewire 3 applications that already own their Tailwind pipeline, and is a poor fit for Inertia/Vue, React front ends, Bootstrap admin panels or apps that ship precompiled CSS.
- How do I install Beartropy UI in a Laravel application?
- Installation is a single composer require beartropy/ui followed by asset publishing, with full installation, configuration and advanced usage documentation hosted at beartropy.com/ui. Before rolling it out, verify the x-bt-* component alias registration against your existing component namespace to rule out collisions. Also confirm whether your Vite/Tailwind sources need to scan vendor/beartropy/ui or whether precompiled assets are published.
- Which Laravel, Livewire, Tailwind and Alpine versions does Beartropy UI support?
- The package material does not state a supported version matrix, and no CI matrix is mentioned. It clearly targets Livewire 3 and the TALL stack, relying on Alpine.data modules and Tailwind class strings delivered through PHP presets. Confirm the tested Laravel, Livewire, Tailwind and Alpine versions with the maintainer before committing to anything beyond a scoped pilot.
- Do I need to compile vendor CSS for Beartropy UI, and how heavy is it?
- This is one of the unproven areas: the documentation does not make clear whether the package publishes precompiled CSS or whether your own Vite/Tailwind build must scan vendor/beartropy/ui. Because styling is expressed as PHP preset arrays rather than Tailwind theme tokens or CSS variables, the class strings live in vendor code and must be picked up by your Tailwind pipeline. Measure the added bundle weight and confirm the asset build story during your pilot.
- Can I customize Beartropy UI colors, presets and dark mode?
- Yes. Colors are defined in PHP preset arrays (presets/*.php) that map color names to Tailwind class strings, so you can retheme by editing or overriding that config array without touching component markup. Dark mode support ships built in, including a ToggleTheme component. Check whether it uses Tailwind's class strategy and whether that conflicts with your existing theme toggle, and confirm presets can be overridden from application config without forking.
- Is Beartropy UI production ready, and what is the maintenance risk?
- Risk here is maturity, not engineering quality: the repository has roughly three GitHub stars and zero dependents, so there is effectively no third-party production validation and you would be among the first real consumers. A changelog and release cadence exist, but a young library at this adoption level typically revises preset keys and prop signatures before 1.0 stabilizes, and each such change is a breaking change inherited inside your Blade templates. There is also no stated test coverage, CI signal, bus factor or security posture for the raw-SVG icon path. Treat it as a scoped pilot rather than a platform-wide commitment.
- Does Beartropy UI work with Livewire 3 and Alpine.js?
- Yes — it is designed for Livewire 3, with class-based Blade components and Alpine components registered through Alpine.data for interactivity. The AI-assistant docs cover Livewire integration patterns explicitly via the /bt-ui-livewire command. Note that adoption is near-atomic per surface: a page either follows Beartropy conventions or it does not, so mixed usage needs planning.
- Is Beartropy UI accessible, and how are SVG icons handled?
- There is no WCAG conformance claim — accessibility is documented per component instead, and the Menu docs do show aria-current, role="list" and sr-only labels, which is a positive indicator. The raw-SVG icon path has no stated security posture. Audit the specific components you intend to use against your accessibility requirements rather than relying on a blanket statement.
- How does the AI assistant support in Beartropy UI work?
- The package ships AI coding-assistant assets: Claude Code slash commands (/bt-ui-form, /bt-ui-component, /bt-ui-livewire, /bt-ui-patterns, /bt-ui-setup), a .cursorrules file you copy from vendor/beartropy/ui/docs/ai-assistants/cursor, a universal BEARTROPY_GUIDE.md and per-component llms/*.md references. Component documentation is unusually concrete, including prop tables, magic attributes, Alpine state and method inventories, and preset key contracts. This is the strongest feasibility signal for integration, since component-level docs are what normally consume the most integration time.
- When should I avoid Beartropy UI, and what are the alternatives?
- Avoid it for Inertia/Vue or React front ends, Bootstrap-based admin panels, and Laravel apps that ship precompiled CSS — it is a poor architectural fit for all three. Because styling lives in PHP preset arrays rather than Tailwind theme tokens or CSS variables, Beartropy becomes a parallel design system rather than an extension of yours, so drift stays invisible until a page renders wrong. The material provided does not name specific competing packages, so evaluate it against other TALL-stack component libraries and against building directly on your own Tailwind tokens.
Weaver
How can I help you explore Laravel packages today?