Weave Code
Filament Common Laravel Package
peltonsolutions/filament-common
Shared utilities and reusable components for Filament admin panels, offering common helpers, form and table conveniences, and small building blocks that keep your Filament projects consistent and reduce duplicated code.
A custom package for Filament that provides common enhancements used throughout peltonsolutions packages.
Frequently asked questions about Filament Common
- What is peltonsolutions/filament-common and what does it actually do?
- It is a small utility package that bundles reusable form fields, table columns, helpers and other building blocks for Filament admin panels. The stated goal is to stop copy-pasting the same components and conventions between projects so multiple panels stay visually and behaviourally consistent. It sits on top of Laravel and Filament rather than replacing them, and it is convention glue rather than a platform or domain layer.
- How do I install filament-common in a Laravel application?
- Install it with composer require peltonsolutions/filament-common from your project root. Because it ships as a Laravel package it will likely register through package auto-discovery, and if it exposes a Filament plugin you may also need to add it to a PanelProvider. There is no published documentation site, so confirm the exact registration steps in the repository README before wiring it into an existing panel.
- Which Filament version does filament-common support, v3 or v4?
- The package does not publish a compatibility matrix, so the supported Filament major is not stated up front. Read composer.json and the service provider to see which Filament, Laravel, PHP, Livewire and Tailwind constraints are actually enforced. Filament introduces breaking changes between majors, so test against the exact version your panel runs before adopting it.
- Is filament-common safe to use in production?
- Mechanically the install is low friction, but the validation signals are thin: no visible test suite, no CI badges, no dependents and a single maintainer. That makes it a reasonable internal convenience layer for non-critical admin screens and a weak choice as a foundational dependency on business-critical panels. Pin the version and read the source before relying on it.
- Is filament-common worth using on a single Filament panel?
- Probably not. The value proposition depends on maintaining two or more Filament admin surfaces and already absorbing real cost from drift between them; on a single panel it is mostly overhead with a vendor namespace attached. Consider it only if you expect more panels or already run a portfolio of Filament applications.
- Does filament-common depend on other peltonsolutions packages or private conventions?
- The package describes itself as common enhancements used throughout peltonsolutions packages, which suggests its helpers may assume sibling packages, naming conventions or config. Whether those are hard Composer requirements or soft assumptions is not documented. Check composer.json and grep the source for class references before assuming it works standalone.
- Is filament-common licensed for commercial use?
- The license and commercial-use terms are not stated in the package description and must be confirmed from the LICENSE file and the composer.json license field. Do not assume MIT just because it is publicly available on Packagist. Get written confirmation from the maintainer if you intend to ship it inside a commercial product.
- Can I adopt only some components of filament-common, or is it all-or-nothing?
- There is no documented guidance on partial adoption. In practice traits, macros and Blade components can usually be used selectively, but base resources or panel plugin configuration may pull in conventions you have to accept wholesale. Read the service provider and directory layout to judge how tightly coupled the pieces are before committing.
- Who maintains filament-common and is it actively developed?
- It is maintained by Peltonsolutions and shows a single visible release, v1.0.1, with no stars, no dependents and no public issue history. Support is therefore a direct maintainer relationship rather than a community one. Ask about release cadence and whether you would be a downstream consumer or a de facto co-maintainer before you build on it.
- What are the alternatives to filament-common for sharing Filament components?
- You can build an internal package of shared Filament fields, columns and actions tailored to your own conventions, which is often the better long-term option for a single organisation. Filament's built-in components and generator commands already cover a lot of the same ground without an extra dependency. Community packages exist for specific concerns, but for general glue an in-house package usually wins on control and support.
Weaver
How can I help you explore Laravel packages today?