Filament v4 Custom Field Plugins with Alpine.js | Mohamed Said [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ ](https://github.com/EG-Mohamed) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ home ](https://msaied.com) [ articles ](https://msaied.com/articles) Filament v4 Custom Field Plugins: Wrapping Third-Party JS Libraries Cleanly On this page 1. [ Why Custom Field Plugins Deserve a Proper Architecture ](#why-custom-field-plugins-deserve-a-proper-architecture) 2. [ Step 1: Scaffold the Field Class ](#step-1-scaffold-the-field-class) 3. [ Step 2: The Blade View with Alpine.js Wiring ](#step-2-the-blade-view-with-alpinejs-wiring) 4. [ Step 3: The Alpine Component ](#step-3-the-alpine-component) 5. [ Step 4: Asset Registration via a Service Provider ](#step-4-asset-registration-via-a-service-provider) 6. [ Step 5: Repeater Compatibility ](#step-5-repeater-compatibility) 7. [ Takeaways ](#takeaways) ![Filament v4 Custom Field Plugins: Wrapping Third-Party JS Libraries Cleanly](https://cdn.msaied.com/650/513b93e06c50ba04f241beb1c3c16aa8.png) #filament #laravel #alpine-js #livewire Filament v4 Custom Field Plugins: Wrapping Third-Party JS Libraries Cleanly ============================================================================= 10 Sep 2026 3 min read ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said Table of contents 1. [ 01 Why Custom Field Plugins Deserve a Proper Architecture ](#why-custom-field-plugins-deserve-a-proper-architecture) 2. [ 02 Step 1: Scaffold the Field Class ](#step-1-scaffold-the-field-class) 3. [ 03 Step 2: The Blade View with Alpine.js Wiring ](#step-2-the-blade-view-with-alpinejs-wiring) 4. [ 04 Step 3: The Alpine Component ](#step-3-the-alpine-component) 5. [ 05 Step 4: Asset Registration via a Service Provider ](#step-4-asset-registration-via-a-service-provider) 6. [ 06 Step 5: Repeater Compatibility ](#step-5-repeater-compatibility) 7. [ 07 Takeaways ](#takeaways) Why Custom Field Plugins Deserve a Proper Architecture ------------------------------------------------------ Dropping a `` tag into a Blade view and calling it a Filament field is a trap. You end up with state that Livewire can't track, assets that load on every page, and a component that breaks the moment someone nests it inside a repeater. Filament v4's schema-based architecture gives you clean extension points — use them. This article walks through wrapping a hypothetical `FancyPicker` JS library into a first-class Filament v4 field plugin. --- Step 1: Scaffold the Field Class -------------------------------- Extend `Filament\Forms\Components\Field` and declare your configuration API: ```php namespace App\Forms\Components; use Filament\Forms\Components\Field; class FancyPickerField extends Field { protected string $view = 'forms.components.fancy-picker'; protected bool $allowMultiple = false; public function allowMultiple(bool $condition = true): static { $this->allowMultiple = $condition; return $this; } public function getAllowMultiple(): bool { return $this->allowMultiple; } } ``` Keep configuration fluent and immutable-friendly. Avoid storing mutable JS state in PHP — that belongs in Alpine. --- Step 2: The Blade View with Alpine.js Wiring -------------------------------------------- Filament v4 passes the component instance into the view. Use `$getStatePath()` and `$getState()` to bind correctly: ```blade @php $statePath = $getStatePath(); $state = $getState(); $multiple = $getAllowMultiple(); @endphp ``` `$wire.entangle(...).live` is the critical line — it creates a two-way binding between Alpine's reactive data and Livewire's component state without any manual event dispatching. --- Step 3: The Alpine Component ---------------------------- Register your Alpine component in a dedicated JS file so it's tree-shakeable: ```javascript // resources/js/fancy-picker.js import FancyPickerLib from 'fancy-picker-lib'; export default function fancyPicker({ state, multiple }) { return { state, multiple, picker: null, init() { this.picker = new FancyPickerLib(this.$refs.picker, { multiple: this.multiple, defaultValue: this.state, onChange: (value) => { this.state = value; // entangle pushes this to Livewire }, }); this.$watch('state', (value) => { // Sync external changes (e.g., form reset) back into the lib if (this.picker.getValue() !== value) { this.picker.setValue(value); } }); }, }; } ``` The `$watch` in the opposite direction handles programmatic state changes — form `fill()`, wizard navigation, or `reset()` calls. --- Step 4: Asset Registration via a Service Provider ------------------------------------------------- Never enqueue assets globally. Use Filament's asset system so they only load when the field is rendered: ```php use Filament\Support\Assets\Js; use Filament\Support\Facades\FilamentAsset; public function boot(): void { FilamentAsset::register([ Js::make('fancy-picker', __DIR__ . '/../../dist/fancy-picker.js') ->loadedOnRequest(), ], package: 'my-org/fancy-picker'); } ``` Then in your field class, declare the asset dependency: ```php public function getExtraAlpineAttributes(): array { FilamentAsset::getScriptSrc('fancy-picker', package: 'my-org/fancy-picker'); return []; } ``` Actually, the idiomatic v4 approach is to call `FilamentAsset::getScriptSrc()` inside the view or override `setUp()` to register a `$livewire->js()` call — check your Filament version's asset API for the exact hook, as it evolved between v4 minor releases. --- Step 5: Repeater Compatibility ------------------------------ Repeaters clone DOM nodes. Your Alpine component must reinitialise on clone. Add a unique key: ```blade ``` `wire:key` forces Livewire to treat each repeater row as a distinct DOM subtree, preventing stale Alpine instances. --- Takeaways --------- - Use `$wire.entangle(...).live` for bidirectional state sync; avoid manual `$dispatch`. - Register assets with `loadedOnRequest()` to keep panel payloads lean. - Always `$watch` the entangled state to handle programmatic form changes. - Set `wire:key` on the root element to survive repeater cloning. - Keep PHP configuration fluent; keep mutable UI state in Alpine only. Found this useful? [ ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fmsaied.com%2Farticles%2Ffilament-v4-custom-field-plugins-wrapping-third-party-js-libraries-cleanly&text=Filament+v4+Custom+Field+Plugins%3A+Wrapping+Third-Party+JS+Libraries+Cleanly) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fmsaied.com%2Farticles%2Ffilament-v4-custom-field-plugins-wrapping-third-party-js-libraries-cleanly) Frequently Asked Questions ---------------------------- 3 questions Q01 Can I use `$wire.entangle` without `.live` for performance? Yes — omitting `.live` defers the Livewire sync to the next network request (e.g., form submission). Use `.live` only when the server needs to react immediately to field changes, such as for dependent field visibility. For most pickers, deferring is fine and reduces round-trips. Q02 How do I handle server-side validation errors in a custom field? Filament's field wrapper component automatically reads `$errors->get($statePath)` and renders them below the field. As long as your Blade view uses `<x-dynamic-component :component="$getFieldWrapperView()" :field="$field">`, validation messages appear without any extra work on your part. Q03 Should the JS asset be compiled into the Filament panel's Vite build or shipped separately? Ship it separately via `FilamentAsset::register()` with `loadedOnRequest()`. Compiling into the panel build creates a tight coupling between your plugin and the consuming application's build pipeline, which breaks for teams using the pre-built Filament CSS/JS. Continue reading More Articles --------------- [ View all ](https://msaied.com/articles) [ ![PostgreSQL Window Functions in Laravel: Ranking, Running Totals, and Gap Detection](https://cdn.msaied.com/649/9ce340f6d71d0052cb3d0eaba1f08754.png) laravel postgresql performance ### PostgreSQL Window Functions in Laravel: Ranking, Running Totals, and Gap Detection Window functions let you compute rankings, running totals, and detect gaps in sequences without subqueries or... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 9 Sep 2026 4 min read Read ](https://msaied.com/articles/postgresql-window-functions-in-laravel-ranking-running-totals-and-gap-detection-2) [ ![Event Sourcing in Laravel: Aggregates, Projectors, and Rebuilding Read Models](https://cdn.msaied.com/647/586a0f822614fed8091917a895ebc502.png) laravel event-sourcing ddd ### Event Sourcing in Laravel: Aggregates, Projectors, and Rebuilding Read Models A practical walkthrough of event sourcing in Laravel — defining aggregates, persisting domain events, building... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 9 Sep 2026 3 min read Read ](https://msaied.com/articles/event-sourcing-in-laravel-aggregates-projectors-and-rebuilding-read-models) [ ![Queue totalSize() and JobInterrupted Event in Laravel 13.31](https://cdn.msaied.com/648/d0e925e5b65d5b1d925fdaf612af5db2.png) Laravel 13 Queue Eloquent ### Queue totalSize() and JobInterrupted Event in Laravel 13.31 Laravel 13.31 ships Queue::totalSize(), a new JobInterrupted event, chaperone support for BelongsToMany pivot... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 9 Sep 2026 3 min read Read ](https://msaied.com/articles/queue-totalsize-and-jobinterrupted-event-in-laravel-1331) [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com)Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow. Explore - [Home](https://msaied.com) - [Projects](https://msaied.com/projects) - [Articles](https://msaied.com/articles) - [Certificates](https://msaied.com/certificates) - [Contact](https://msaied.com#contact-section) Connect - [ hello@msaied.com ](mailto:hello@msaied.com) - [ +20 109 461 9204 ](tel:+201094619204) © 2026 Mohamed Said. All rights reserved. [ ](https://github.com/EG-Mohamed) [ ](https://www.linkedin.com/in/msaiedm/) [ ](https://wa.me/201094619204) [ ](mailto:hello@msaied.com) [ ](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view)