Weave Code
Laravel Dashboard Time Weather Tile Laravel Package
spatie/laravel-dashboard-time-weather-tile
A Laravel Dashboard tile that displays the current time and weather together in one widget. Install it via Composer and add it to your dashboard config. Documentation lives on the Spatie dashboard docs site.
spatie/laravel-dashboard-time-weather-tile is a compact tile for the Laravel Dashboard that combines a live clock and current weather in one widget. It lets you add glanceable time and weather information to your dashboard without building a custom tile.
- Displays the current time directly on your dashboard
- Shows weather conditions alongside the clock
- Integrates with the Laravel Dashboard tile system
- Installed via Composer and maintained by Spatie
- Released under the MIT license
Frequently asked questions about Laravel Dashboard Time Weather Tile
- How do I install spatie/laravel-dashboard-time-weather-tile in Laravel?
- Install it with Composer using composer require spatie/laravel-dashboard-time-weather-tile, then register the tile in your Laravel Dashboard configuration. You can optionally publish the views if you need to override the default Tailwind styling. The package assumes spatie/laravel-dashboard is already installed and configured.
- Which Laravel Dashboard version does this tile require?
- The tile major version must match your dashboard major version. Tile 4.x requires spatie/laravel-dashboard v4, 3.x aligns with dashboard v3, and 2.x was for dashboard v2. Pin both packages together so a dashboard upgrade includes the matching tile upgrade.
- Does this tile work with PHP 8 and modern Laravel versions?
- PHP 8 support landed in tile 2.0.1, so current 4.x releases are safe on PHP 8. Laravel version support comes mainly from the host spatie/laravel-dashboard v4 package, so verify that package's requirements. The tile itself is a presentation-layer card and does not add framework-level constraints beyond the dashboard.
- How do I change the timezone shown on the clock?
- Since release 4.1.0 the clock inherits config/app.timezone, so set your application timezone normally. That fixes the common wrong-hour issue for distributed teams with a single app timezone. Per-user timezone overrides are not provided by the tile, so you would need custom code if different users require different clocks.
- Which weather provider does this tile use and what coverage does it have?
- The tile uses an external weather source that historically points at Buienradar, not a commercial provider with an API key or SLA. That means no key procurement but also Netherlands-centric coverage and an undocumented upstream. Validate coverage for your users' geography; if it does not fit, the tile may effectively become just a clock.
- Can I change temperature units or show inside temperature?
- Temperature units have been configurable since 1.1.0, and since 1.3.0 you can configure an optional inside-temperature endpoint. If you do not set that endpoint, the inside temperature span correctly hides. Check the dashboard tile config for the exact keys in the version you pin.
- How do I customize the tile's Blade view and styling?
- You can publish the tile views and override the Blade markup and Tailwind classes to match your design system. That is optional; defaults work for quick internal dashboards. If you publish views, treat them as maintained code because future tile updates may require view adjustments.
- What happens if the weather API is down or returns bad data?
- Since 1.3.1 the tile degrades instead of crashing when weather data is unavailable, but degraded can mean a blank or stale weather display. The clock can continue to work independently. Decide your failure posture: silent degradation, a stale-data indicator, or hiding the weather portion when the upstream is down.
- How do I test the tile in my Laravel app?
- The repository documents composer test for its own test suite. In your application, test that the tile is registered and renders within the dashboard, and mock or avoid live weather HTTP calls. Because upstream weather is external and undocumented, do not make CI depend on real provider responses.
- Are there alternatives, or should I use this for weather forecasts and history?
- This is not a forecasting, historical weather, or interactive weather package; it has no trends, forecasts, or interactivity. If stakeholders need weather analytics, choose a commercial weather API and build a custom tile. Use this package when you want a compact time-and-weather affordance inside an existing Spatie dashboard.
Weaver
How can I help you explore Laravel packages today?