- How do I install the Nova Custom Table Card in Laravel?
- Install the package with Composer using m-a-k-o/nova-custom-table-card, then run php artisan nova:publish if frontend assets need publishing. Register the card in NovaServiceProvider::cards() or inside a Nova Dashboard class. No migrations are required for the basic case. Verify the exact configuration methods against the installed vendor source during a short spike.
- Which Laravel, PHP, and Nova versions does this card support?
- The package is intended for Laravel applications that already use Laravel Nova, but exact supported versions should be checked in composer.json and any CI configuration. Because it is a low-adoption package, confirm the Nova major version, Laravel version, PHP version, and frontend asset compatibility before adopting it. Test dashboard and resource-page rendering, dark mode, and responsive behavior in a non-production environment. Pin the version once compatibility is confirmed.
- How do I configure the model or query shown in the card?
- The card is configured with a model or query plus columns, labels, ordering, and a row limit. The exact API surface may drift on a low-adoption package, so verify method names such as model(), columns(), limit(), and orderBy() in vendor/m-a-k-o/nova-custom-table-card rather than relying only on the README. Keep the configured query read-only and scoped to the records the dashboard should display.
- Can I format columns and add row links in the custom table card?
- The package is positioned for building custom data tables with control over columns, queries, and formatting. Row links, empty states, localization, and specific formatter behavior should be validated against the installed version because the public documentation is limited. Use the card for familiar tabular displays where formatting needs are straightforward. If stakeholder expectations require advanced drill-downs or exports, consider a native Nova resource or custom card instead.
- How do I limit the number of rows and keep dashboard performance acceptable?
- Configure a bounded row limit and order by the latest records so the card renders a small recent dataset such as orders, posts, signups, or failed jobs. Ensure the underlying query uses appropriate indexes and avoid unbounded scans on large tables. Cache the query result if dashboard render time becomes a concern. Agree on a render-time threshold and test the card against production-like data volumes.
- Can I control who sees the card with Nova policies or canSee()?
- The card inherits typical Nova card behavior such as canSee() and onlyOnDetail(), but you should verify those hooks in the installed source before relying on them. Apply Nova policies and Eloquent scopes to constrain the query, and enforce tenant or user scoping in the query itself rather than only in the UI. Tenancy enforcement and authorization hooks are unproven until tested for this package. Treat visibility as a security concern, not just a presentation preference.
- Is there a test suite, and how should I test this Nova card?
- The package has a small code footprint, but a published test suite and CI coverage should be confirmed in the repository before adoption. Test installation, card registration, query scoping, row limits, formatting, empty states, dark mode, and permissions in a non-production Nova environment. Verify the rendered output against each dashboard placement you plan to use. Because community validation is limited, your own smoke tests are essential.
- Is the Nova Custom Table Card safe to use in production?
- It is acceptable for internal admin convenience when pinned, validated, and backed by a documented native-card fallback. The positives are an MIT license, a recent 2025 release, a small read-only footprint, and low integration effort for Nova teams. The risks are low adoption, single-maintainer continuity, unproven Nova major-version compatibility, and untested authorization or tenancy behavior. Avoid it for customer-facing analytics or any dashboard where an outage becomes a business incident.
- What is the best alternative if this package does not fit?
- Replace it with a native Nova custom card or a simple Nova resource table backed by the same read-only query contract. Because adoption is a UI-only addition with no data migration, the decision is reversible and sunk cost is small. Capture the fallback plan in writing before the first production deploy. This keeps the product decision flexible if the package stalls or breaks on a Nova upgrade.
- Who maintains the package, and what is the release cadence?
- The repository is a single-maintainer package with roughly 45 stars and no dependents, so community validation is minimal. A recent release date of 2025-09-23 is positive, but ongoing responsiveness and release cadence should be checked before committing to critical dashboards. Pin the version and identify who owns a fork or native replacement if maintenance stalls. Treat maintainer continuity as a real adoption risk rather than a hypothetical one.