Weave Code
Nova Filterable Cards Laravel Package
beyondcode/nova-filterable-cards
Nova Filterable Cards lets you add interactive, filterable cards to Laravel Nova dashboards. Define metrics and filters so users can quickly narrow results by date range or custom criteria, making dashboard insights more flexible. Simple to configure and ideal for dashboards that need more than stat...
Filterable metric cards for Laravel Nova.
Frequently asked questions about Nova Filterable Cards
- What is beyondcode/nova-filterable-cards used for?
- It is a Laravel Nova card extension for adding interactive, filterable metric cards to Nova dashboards. You define metrics and filters so dashboard users can narrow results by date range or custom criteria without building a separate reporting UI. It is not a general Laravel package; it only matters if your admin panel runs Laravel Nova and needs per-card filtering that native Nova filters do not cover.
- Does beyondcode/nova-filterable-cards support Laravel Nova 4 or Nova 5?
- No. The package pins laravel/nova ^1.0 and php ^7.1 with Laravel 5.6 or 5.7, and its Vue 2 frontend does not survive Nova 4/5's Vue 3 transition. Composer require will fail on a current stack, and --ignore-platform-reqs just moves the failure to a blank or broken card in production. Treat it as a reference design, not a dependency, for Nova 3 and later.
- How do I install beyondcode/nova-filterable-cards?
- The historical path was composer require beyondcode/nova-filterable-cards, but that is not realistic on a current Laravel and Nova stack because of hard version pins. There is also no service provider asset registration; it is a library of card classes registered in NovaServiceProvider::cards(). For modern Nova, do not install it; copy the small PHP and Vue pattern and reimplement against current Nova card scaffolding.
- Why is beyondcode/nova-filterable-cards archived and is it still maintained?
- The repository is archived with one experimental release from August 2018, a single maintainer, 58 stars, and zero dependents. There is no security response path, no compatibility work inbound, and no maintenance. Any build that references the GitHub URL as a Composer vcs repository also creates a supply-chain risk because deletion breaks builds.
- Can I use beyondcode/nova-filterable-cards in production?
- Not on a current stack. The package targets Nova 1.x and Laravel 5.6 or 5.7, has negligible field testing, and any defect will surface first in your environment. The defensible production path is a clean-room reimplementation or an internal fork that you own, with a defined filter contract for date boundaries, timezones, tenant and policy scoping, and composition with native Nova filters.
- How does the filtering work in Nova Filterable Cards?
- The card reads Nova's dashboard filters query parameter, decodes it, and replays each filter's apply method against the card's metric query. That scopes the card's numbers to the selected criteria while the Vue 2 filter control sits in the card header. The pattern is simple and conventionally structured, which is why it works well as a reference for a modern rebuild.
- What are the alternatives to beyondcode/nova-filterable-cards for Laravel Nova dashboards?
- First check native Nova filter-refresh behavior, especially refreshWhenFiltersChange in Nova 3 and later, because it duplicates most of this package's reason to exist. For per-card date ranges or custom criteria that native filters cannot express, build a small custom Nova card using current scaffolding. If you need cross-card filtering, saved views, drill-downs, or export, use a BI tool such as Metabase, Looker, or Redash instead of a Nova card.
- What Laravel and PHP versions does beyondcode/nova-filterable-cards require?
- It pins php ^7.1, laravel/framework 5.6 or 5.7, and laravel/nova ^1.0. Those constraints are from the 2018 release and do not reflect current Laravel or Nova versions. On PHP 8 or Laravel 10 and later with Nova 4 or 5, dependency resolution will fail before you can evaluate the card behavior.
- How should I migrate from beyondcode/nova-filterable-cards to a supported solution?
- Reimplement in-house against current Nova card scaffolding; for a Nova-familiar developer this is roughly a one-to-two-day clean-room build. Extract the filter contract from the reference code, then define dimensions, policy and tenant scoping, native-filter composition, date inclusivity, and timezone policy yourself. Vendoring is only defensible for a genuinely pinned Nova 1.x and Laravel 5.x app, and even then mirror the repository rather than depending on the archived GitHub URL.
- What should I check before using filterable metric cards in Laravel Nova?
- Confirm which Nova major you run and whether a Nova upgrade is funded, because Nova 3 and later native filters may already satisfy the requirement. Clarify the exact unmet need: per-card date range, plan, channel, tenant, or broader BI features like saved views and drill-downs. Also verify the queries behind the cards, index the filtered timestamp columns, and decide whether you will own a permanent internal fork rather than depend on archived upstream.
Weaver
How can I help you explore Laravel packages today?