Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Filament World Clock Laravel Package

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.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Admin-panel and internal-tooling roadmap. The package is a Filament plugin that hooks into Filament's page and routing layer (the v3.0.2 change is driven by the new 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.
  • Build vs. buy for custom panel pages. If the alternative is hand-rolling routing, navigation registration, and page lifecycle wiring on top of Filament, this package is a "buy" that removes boilerplate. The decision hinges on how much of your panel is non-CRUD pages — if most of your admin surface is plain Filament resources, the marginal value drops sharply.
  • Framework-version gating as a product constraint. v3.0.2 raises the floor to 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.
  • Vendor and upgrade-cost budgeting. The 3.0.x line tracks Filament's internals closely (this bump exists solely to follow an upstream signature change). That is a recurring maintenance line item, not a one-time integration cost — plan capacity for it each time Filament ships a minor that touches page routing.

When to Consider This Package

Adopt when:

  • You are already on, or committed to, Filament ^5.3. Anything below that is a hard incompatibility as of v3.0.2.
  • Your panel needs custom pages beyond stock Filament resources — pages that carry their own routes, navigation entries, and configuration.
  • You want upstream tracking handled by a maintainer rather than owning the Page::routes() override yourselves.
  • The alternative is genuinely more expensive than the dependency: a small team without spare capacity to babysit Filament internals.

Look elsewhere when:

  • You are pinned to Filament 5.0–5.2 or earlier for other plugin reasons. Upgrading Filament to satisfy this plugin may cost more than the plugin saves; sequence the Filament upgrade first and revisit.
  • Your admin surface is standard CRUD resources only — you likely do not need the extension point at all.
  • You are not on Filament, or your panel is Blade/Livewire-first. This is not a general Laravel package; it has no value outside that ecosystem.
  • You need long-term-support stability. A package that must republish a breaking version for every upstream signature change is a moving target. If your release cadence cannot absorb that, prefer a fork you control.

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.

How to Pitch It (Stakeholders)

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.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
diephp/sequences
users-au/socialite-provider
twidpay/twid-logger
mrnewport/laravel-plaid
mrnewport/laravel-repo
mrnewport/laravel-docsign
mrnewport/laravel-stow
mrnewport/laravel-flow
mrnewport/laravel-priceable
mrnewport/laravel-nestedterms
fredmeng/laravel-apidoc-generator
itstructure/laravel-multilingual-tools
pdustdar/elasticsearch
markupai/php-sdk
rlacerda83/lumem-microservice-shipment
uni-method/symfony-lib
tacticmedia/scim-server-bundle
neika-ai/symfony-bundle
mattleads/agent-publishing-bundle
glavweb/framework-bundle