joaopaulolndev/filament-world-clock
A Filament plugin that adds a customizable world clock widget to your admin panel. Display current local times across multiple timezones, choose clock styles, and configure labels and layout for a clean, dashboard-ready overview—ideal for distributed teams and global schedules.
PageConfiguration parameter on Page::routes()). Any roadmap item that ships operator-facing screens inside a Filament panel is a candidate use case: settings pages, approval queues, custom dashboards, tenant-scoped resource screens.filament/filament: ^5.3. That means adoption is coupled to a Filament 5.3+ upgrade. Treat this as a schedule dependency: the plugin can only land after the panel upgrade lands, not in parallel.Adopt when:
Page::routes() override yourselves.Look elsewhere when:
Before adopting, verify: the package's actual feature surface against your use case, its test coverage against Filament 5.3, and whether it declares a maximum Filament constraint or only a minimum.
To executives: This is a small dependency that speeds up building the internal admin screens our operations team uses — it removes custom plumbing we would otherwise write and maintain ourselves. The cost is a version-coupling constraint: it now requires Filament 5.3 or newer, so it becomes part of the Filament upgrade workstream rather than something we can drop in independently. No user-facing impact on its own.
To engineering: v3.0.2 is a breaking release in the practical sense — the minimum Filament version is now ^5.3, required by the new PageConfiguration parameter in Page::routes() (filamentphp/filament#19225). Pin accordingly. If we are below Filament 5.3, upgrading this package will fail dependency resolution, so order the work: Filament upgrade first, plugin bump second. Expect this pattern to repeat — the 3.x line tracks Filament internals, so treat each Filament minor as a potential plugin bump and keep the constraint range explicit in composer.json rather than floating. Recommend we validate our own custom pages against the new routes() signature in a branch before merging, and confirm the package's upper bound on Filament so an unexpected 5.4 does not break the panel silently.
How can I help you explore Laravel packages today?