- What is andrefelipe18/tallstackuifilament used for?
- It is a thin adapter that lets you render TallStackUI Blade components inside Filament forms, so an admin panel can share the same component vocabulary as a TALL-stack application. It is cosmetic and ergonomic rather than a new capability: Filament's tables, actions, and workflows stay Filament's. It only makes sense if your Laravel app already uses both Filament and TallStackUI.
- How do I install TallStackUI Filament in a Laravel app?
- Install with Composer using composer require andrefelipe18/tallstackuifilament. Laravel package auto-discovery should register the service provider; check the README for any optional vendor:publish step for config or assets. The assessment describes installation as mechanically trivial and additive, with no data-model or routing changes.
- Which Filament versions and TallStackUI versions are supported?
- The provided context does not document a definitive support matrix. The assessment warns that adapter packages couple two independently versioned upstreams, so confirm the exact Filament major and TallStackUI version in the source or with the maintainer. Pin all three packages and add a CI job that installs the pinned trio and renders a smoke page.
- Does TallStackUI Filament work with Filament v4?
- There is no confirmed v4 compatibility in the context provided. The assessment explicitly flags Filament's v3-to-v4 transition as likely to require adapter changes, because the package bridges two independently versioned upstreams. Treat v4 support as unverified until you see it tested in CI or confirmed by the maintainer.
- Does TallStackUI Filament only cover form fields, or tables and actions too?
- The package description says it is for Filament forms, which suggests form inputs and buttons rather than the whole panel. The assessment lists tables, actions, modals, notifications, and layout as open questions to confirm. Review the source or render representative components before assuming broad coverage.
- Is TallStackUI Filament safe for production?
- It is MIT-licensed and small, so vendoring or forking is cheap, but it has a single maintainer, about 10 stars, and zero dependents, meaning no public production signal. You are effectively the QA function: pin versions and render a smoke page in CI. The assessment calls abandonment survivable because the surface area is small.
- How do I avoid Tailwind CSS conflicts between Filament and TallStackUI?
- Both Filament and TallStackUI ship Tailwind configuration, so duplicate utilities, content-path conflicts, and purge surprises are a realistic risk. Check whether the package adds a Tailwind preset or publishable assets and reconcile content paths in your build. A rendered smoke page in CI is the practical way to catch styling regressions that unit tests miss.
- How should I test TallStackUI Filament before deploying?
- Install the pinned trio of Laravel, Filament, and TallStackUI, then render a smoke page with representative components such as a text input, select, modal, table column, and row action. The assessment recommends a one-to-two-day compatibility spike and a CI job that installs exact versions and renders. Do not rely on a green Composer install alone; the failure mode is subtly broken styling.
- What are alternatives to TallStackUI Filament?
- Use Filament's native Blade components and keep TallStackUI for the public app, accepting two vocabularies. Wait for native TallStackUI support in Filament upstream if it arrives, or copy the small adapter into your app if you only need a bounded set of wrappers. The assessment also suggests confining usage so removal is a sprint rather than a quarter.
- Is TallStackUI Filament actively maintained?
- The context shows a single maintainer and low adoption, so check the release cadence and issue responsiveness over the last six months before adopting. The MIT license and small code surface make forking or vendoring realistic if the package stalls. Do not assume it will track Filament major releases promptly.