Weave Code
Filament Password Input Laravel Package
parfaitementweb/filament-password-input
An enhanced password input component for Filament that adds a reveal-password toggle, copy-to-clipboard button, and a generate-new-password action. Drop-in replacement for Password::make() with no config or migrations required.
An enhanced password input component for Filament forms, parfaitementweb/filament-password-input extends the standard password field with user-friendly tools for entering and managing credentials. Drop-in replacement for Password::make(), it requires no configuration files or migrations, and options can be set per-input or globally via a service provider.
- Reveal toggle to show or hide the typed password
- Copy to clipboard button for quick reuse
- Generate password button for strong new credentials
- Global configuration shared across all password inputs
- Publishable translations for localized labels and tooltips
Frequently asked questions about Filament Password Input
- How do I install filament-password-input in a Laravel Filament app?
- Install it with composer require parfaitementweb/filament-password-input. There is no service provider, config file, or migration to run. Then import Parfaitementweb\FilamentPasswordInput\Password and use Password::make('password') in your Filament form schema, optionally chaining methods such as label(). For existing forms, replace TextInput::make('password')->password() with the new field.
- Does filament-password-input need a config file or migrations?
- No. The package ships no configuration file and no migrations, so installation is just the Composer require. Customization happens on the field itself or globally through Password::configureUsing() in a service provider. The only publishable assets are translation files, which are optional.
- Which Filament and Laravel versions does filament-password-input support?
- The package's version line follows Filament majors: v4.0.0 was the Filament 4 update and v4.1.0 allows a Filament 5 dependency. It targets Laravel applications running Filament 4.x or 5.x on PHP 8.2 or newer. It does not promise support for older Filament majors, so confirm the Composer constraint against your installed Filament version before adopting it.
- How do I show a reveal/hide toggle on a Filament password field?
- Use the package's Password field instead of a plain TextInput with ->password(). The reveal/hide toggle is one of the built-in opt-in affordances and is rendered as an action inside the input using Blade and Alpine, so no extra JS build step is required. You can enable it per field or set it once for every password input via global configuration.
- Can I set default password input options globally in a service provider?
- Yes. In AppServiceProvider's boot method, call Password::configureUsing() with a closure that applies your house defaults to every instance of the field. That lets you standardize reveal, copy, and generation behavior across all Filament panels with one block of code instead of editing each form. It is the recommended lever for teams rolling the component out broadly.
- How do I enable copy to clipboard and generate password buttons?
- The field exposes fluent methods for the optional affordances; copy to clipboard is enabled with copyable(), and the generator adds a button that creates a password server-side through Livewire. Both are opt-in, so you can enable them only on fields where operators are allowed to see or copy the credential. Because generated plaintext round-trips through the Livewire payload and copied values land on the OS clipboard, treat enabling them as a security policy decision, not just a UI choice.
- Is filament-password-input safe to use in production admin panels?
- Functional risk is low because it is a presentation-only Filament field with no migrations, persistence, or domain logic. The real risk is supply chain: it is a small, low-star, effectively one-maintainer project whose version line tracks Filament majors, so a Filament upgrade can break it. Mitigate by pinning versions, reviewing the few Blade and Alpine files, disabling generation or copy where policy requires, and accepting that an MIT-licensed fork is a few hours of work if upstream goes quiet.
- How do I override the filament-password-input language lines?
- Publish them with php artisan vendor:publish --tag=filament-password-input-translations and override the lines in your application's lang files. This is optional; the package works without publishing anything. It is useful when you need labels or tooltips for the reveal, copy, and generate actions in another language or in your own wording.
- How do I test the password input component in my Filament application?
- You do not need special test infrastructure because the package adds no routes, migrations, or storage. In your app's Filament form or Livewire tests, assert that the field renders and that the enabled actions behave as expected for the roles that can see them. A pilot on one panel plus a QA pass is typically under a day for a Filament-fluent developer, and the package's own test suite is visible via its GitHub Actions badge.
- What are alternatives to filament-password-input if it is abandoned?
- The native option is Filament's TextInput with ->password() and whatever reveal support your Filament version provides; you would then hand-roll copy and generation with Blade and Alpine. This package wraps those affordances as a drop-in field under the MIT license, so forking and self-maintaining is realistic given the tiny surface area. If you need audit hooks for reveal or copy events, plan for a fork or wrapper because the package exposes none.
Weaver
How can I help you explore Laravel packages today?