- How do I install tangodev-it/filament-emoji-picker in a Laravel app?
- Install it with Composer using composer require tangodev-it/filament-emoji-picker, then register the plugin in your Filament PanelProvider or apply the field method to an existing input, publish the package assets, and rebuild your admin assets. The provided excerpt does not include the exact namespace or registration snippet, so confirm those details in the package README or source before rolling it out.
- Which Laravel and Filament versions does this emoji picker support?
- The overview does not state version constraints. The technical assessment assumes Laravel 10/11+, PHP 8.1+, Filament v3.x, and Livewire 3, but you must verify the actual composer.json constraints. Pin the package and Filament versions in composer.lock so an update does not change picker behavior unexpectedly.
- Can I use the emoji picker on a TextInput, Textarea, or RichEditor in Filament?
- The package is described as adding a searchable emoji picker field to Filament forms and input fields, so it is intended for form inputs. The assessment notes it may be implemented as a dedicated Field class or a macro on an existing TextInput or Textarea, and whether it also works as a RichEditor toolbar button is not confirmed. Check the source or README for the exact supported contexts before standardizing on it.
- Does the emoji picker support search and categories?
- Yes. The package is described as a searchable emoji picker where users can browse categories or search, select an emoji, and save it to a model. That makes it suitable for reaction pickers, status fields, and other custom form inputs. Verify the exact keyboard and search behavior in the source if accessibility is a hard requirement.
- How do I save the selected emoji to a model with Filament Emoji Picker?
- Use it as a normal Filament form field: the selected emoji becomes the field state and is saved to the model attribute when the form is submitted, just like text input. No separate storage layer is mentioned. Make sure the target column can store 4-byte UTF-8 emoji.
- Do I need utf8mb4 database columns to store emoji from this picker?
- Laravel defaults to utf8mb4 on modern MySQL and MariaDB, and emoji storage is usually fine; Postgres does not have the same 3-byte utf8 limitation. Any legacy utf8 three-byte column, index prefix, or export can truncate or error on emoji. Check every column that will receive picker output and convert to utf8mb4 if needed.
- Will tangodev-it/filament-emoji-picker work with Filament v4?
- The provided material does not confirm Filament v4 support. Filament v3 to v4 was a breaking release for plugins, including asset registration and field APIs, so a package pinned to v3 can block an upgrade. Treat v4 compatibility as an open question and verify the composer.json constraints before adopting it.
- Does the emoji picker add JavaScript assets or fetch a remote dataset, and can CSP block it?
- The excerpt does not say whether the picker bundles its emoji dataset or fetches one at runtime, or how large the added JavaScript payload is. Client-side pickers that inject inline styles or call remote endpoints can collide with a strict Content-Security-Policy. Review the asset registration and network behavior in the source before deploying to a CSP-restricted admin panel.
- Is this package maintained and safe enough for production?
- The repository URL is unknown, the vendor is a single package, and the listing shows 26 stars with no visible release cadence, so treat it as unvetted until you read the source. Runtime risk is low because the package is presentation-layer only, but supply-chain risk is moderate; check the licence, tagged releases, tests, CI, and dependency graph. Freeze it in composer.lock and review before upgrades.
- What can I use instead of Filament Emoji Picker if I need a more proven option?
- Alternatives include the operating system emoji input, a small custom Filament field wrapping a maintained JavaScript picker such as emoji-mart or emoji-picker-element, or another Filament-compatible emoji picker that declares v3 or v4 support. The right choice depends on whether you need searchable categories, CSP-safe bundling, keyboard accessibility, and a tagged release cadence. If you build a custom field, you control the dataset and upgrade path.