- How do I install idf/nova-worldclock-card in a Laravel Nova application?
- Install it with Composer using composer require idf/nova-worldclock-card, then register the card in the cards() array of your app/Nova/NovaServiceProvider.php. The package is a single Nova card class plus a Vue component, so there are no migrations, routes, or config files to publish. Package discovery should register the service provider automatically. After that, reload the Nova dashboard and the clock card should render.
- Does this card support Laravel Nova 4 and Nova 5?
- You need to verify this before committing, because Nova 3 used Laravel Mix with Vue 2 while Nova 4 and 5 moved to Vite with Vue 3. A card built for the older stack will not mount in the newer one, and the failure is typically a blank card rather than a Composer conflict. Check the laravel/nova constraint in the package composer.json and confirm which Vue major the component targets. Then match both against the Nova version your application has pinned.
- Will I need to compile the card's JavaScript assets myself?
- That depends on whether the package ships prebuilt dist assets or expects the host application to build them. Look for a compiled dist directory in the repository and check how the card's service provider registers its scripts and styles. If prebuilt assets are included, adoption is a five-minute change. If not, your deploy pipeline has to run the Node and Vite build for the card, which turns it into a CI change rather than a Composer-only change.
- Do I need to publish a config file or run database migrations?
- No. This package has no models, migrations, routes, service bindings, middleware, event listeners, or config publishing. Its entire surface area is a Nova card class extending Laravel\Nova\Card plus the registered Vue component. It is strictly a presentational widget inside Nova's authenticated admin UI, so it cannot touch your database or interfere with domain code.
- How do I display multiple time zones on the same card?
- Clock configuration is handled in PHP when you instantiate the card, so you add the time zones you want and pass them through the card's configuration API. Check the card class in the repository for the exact method names and expected format, such as a list of time zone identifiers and labels. Each entry is then rendered as a separate clock in the Vue component. If you need different clocks for different teams, you can register multiple card instances on the dashboard.
- Is the world clock accurate across daylight saving time changes?
- Correctness depends on the implementation. If the clock delegates to Intl.DateTimeFormat or a library like moment-timezone, DST transitions are handled by the browser or the tz database. If it hand-rolls fixed UTC offsets, times will drift by an hour for part of the year in DST-observing regions. Because distributed teams will trust this widget for scheduling, test a DST boundary explicitly before rolling it out.
- Is it safe to add this card to a production Nova dashboard?
- The blast radius is deliberately small. The realistic worst case is a blank card or a JavaScript console error on the Nova dashboard, not an application failure, since the card cannot alter request lifecycle behavior or touch application data. The two things that actually carry production risk are Nova major-version compatibility and whether your deploy pipeline builds the card's assets. Both are verifiable in a staging environment in under an hour.
- Do I need a paid Laravel Nova license to use this package?
- Yes. Nova is a commercial, per-site licensed admin panel, and this card only runs inside it. The card itself is MIT licensed, but that does not remove the Nova prerequisite. If your application does not already run Nova, installing a paid admin panel just to get a clock widget is not a defensible trade, so build a small custom dashboard component instead.
- How do I remove the card if I decide not to keep it?
- Removing it is fully additive in reverse: run composer remove idf/nova-worldclock-card and delete the single entry from the cards() array in NovaServiceProvider. There is no schema to revert, no data to backfill, and no route or config changes to undo. That makes this one of the cheapest possible reversal profiles, which lowers the cost of trialing it and walking away.
- Is this package actively maintained, and what are the alternatives?
- The project has a small footprint, roughly eight stars, zero dependents, and a single organizational maintainer publishing under MIT with no SLA, so treat it as an internal utility open-sourced as a courtesy. The listed last release date is future-dated, which is a metadata anomaly and should reduce your confidence in its dependency-health signals. Realistic alternatives are writing a small custom Nova card yourself, which is a genuinely modest amount of Vue and PHP, or reusing an existing dashboard component outside Nova. Pin the version you evaluate and review the diff before upgrading.