- What is joerithegreat/nova-table-card used for?
- It is a Laravel Nova card that renders a configurable table directly on a Nova dashboard, so you can surface key records, query results, or metrics in clean columns with custom formatting. It is a presentation-layer extension, not a core domain dependency, and it only makes sense in an application that already uses Laravel Nova. Use it to avoid hand-building a custom card for simple tabular or stat-based panels.
- How do I install joerithegreat/nova-table-card with Composer?
- Require the package with Composer on a feature branch first so you can inspect any lockfile changes and confirm the constraints resolve against your Nova, Laravel, and PHP versions. After installing, register the card class in the cards method of the Nova dashboard or resource where it should appear, and publish or refresh the package assets if the release notes call for it. Then load the dashboard in a non-production environment and confirm the table renders as expected.
- Does joerithegreat/nova-table-card support Laravel Nova 5?
- Yes. Release 1.1.0 is a compatibility-focused minor release that adds Laravel Nova 5 support, and the notes state no breaking changes, deprecations, or migration steps. For teams already on Nova 5, this removes the previous compatibility blocker. As always, verify the package's Composer constraints resolve cleanly against your existing lockfile before merging.
- Is version 1.1.0 backward compatible with Nova 4?
- The release notes do not confirm whether 1.1.0 is dual-compatible with Nova 4 and Nova 5. If you are staying on Nova 4, either defer the upgrade or test the new version in a branch to confirm it still works before committing. Teams moving to Nova 5 should sequence the Nova upgrade first, then adopt 1.1.0 as the matching compatibility release.
- How do I register the table card in a Nova dashboard?
- Add the card to the cards method of the dashboard or resource where it belongs, referencing the package's card class and any configuration options you need. Check the README for the exact namespace and configuration signature, since those details matter more than the general pattern. After registering, test the dashboard with different user roles to make sure the card appears where intended.
- Can I customize the columns and formatting in nova-table-card?
- Yes, the card is designed to be configurable, letting you define which columns appear and apply custom formatting to the underlying query results or metrics. That is the main reason to use it instead of a hard-coded custom card. Keep the configuration explicit and version-controlled so dashboard changes are reviewable like any other code.
- Will a Nova table card slow down my dashboard on large datasets?
- The package itself is unlikely to be a scaling bottleneck, but a table card can become one if it runs heavy queries or renders large result sets every time the dashboard loads. Review pagination or row limits, eager loading, database indexes, caching, and query timeouts before putting it on a high-traffic dashboard. Test with realistic data volumes rather than a small development database.
- Does the card respect Nova authorization and resource policies?
- The release notes do not document how the card handles authorization, so verify this yourself before exposing sensitive records on a shared dashboard. Gate access with Nova's authorization mechanisms and test the card as a non-admin user to confirm no data leaks through the dashboard. Treat any card that runs raw queries as a potential data exposure surface.
- Do I need to republish assets after upgrading to 1.1.0?
- It is not confirmed whether the frontend assets changed in this release. Check the changelog and compare the published assets after upgrading, and republish or refresh compiled assets if the package requires it. Stale assets are a common cause of Nova UI rendering errors after an upgrade.
- Is joerithegreat/nova-table-card actively maintained, and what are the alternatives?
- The package is small and UI-oriented, so operational burden is low, but it still creates an upstream dependency in your admin surface, and the terse release notes make long-term support unclear. Track releases and Nova major-version changes, and keep a rollback path to the previous lockfile. If you need more control, the alternatives are building a custom Nova card yourself or using Nova's built-in metrics and table-style cards, at the cost of more setup work.