- How do I install demency/nova-gridder in a Laravel Nova resource?
- Install it with Composer and then reference the Gridder field class inside your Nova resource's fields method, nesting the fields you want to lay out. It is a Nova field, so there are no migrations or domain-code changes beyond standard package registration. Check the package's composer.json constraints first, because the last release dates from June 2021 and targets the Nova 3 era.
- Does nova-gridder work with Laravel Nova 4 or Nova 5?
- Almost certainly not unmodified. The 2021 release predates Nova's move to Vite, Vue 3 and Tailwind 3, and Gridder overrides Nova's internal detail rendering, which is an undocumented and version-sensitive surface. Treat it as close to drop-in on Nova 3 and as a port project on Nova 4 or 5. Prototype on a scratch branch before committing to it.
- Which Laravel and PHP versions does nova-gridder support?
- The realistic fit is Laravel 8 or 9 with Nova 3.x, PHP 8.0 or 8.1 and Tailwind 2. Verify the constraints in the package composer.json rather than assuming forward compatibility from the README. Environments standardized on Vite, Vue 3 and Tailwind 3 are a poor fit.
- How do I arrange Nova fields into responsive columns with Gridder?
- Gridder wraps fields in a Tailwind grid container, so you nest the Nova fields you want inside it and express column spans per breakpoint in your resource PHP. Responsive behavior comes from Tailwind's grid classes, and the layout stays in the resource definition rather than in Blade templates you maintain. You need to confirm the exact configuration syntax against the package source for your Nova version.
- Is demency/nova-gridder still maintained?
- The last tagged release is from 2021-06-28, it has a single maintainer and a small star count, and there is no visible test suite or CI. In practice it is an abandoned micro-package. If you adopt it, plan to vendor it through a private fork or path repository and pin the exact commit.
- Will nova-gridder's Tailwind CSS conflict with Nova's styling?
- It can. Gridder ships Tailwind-based styling that loads alongside Nova's own compiled CSS, so class purging, specificity and light or dark mode behavior may diverge between development and production builds. Review the published CSS for global selectors that could leak into other Nova screens, and verify the result in a production build.
- Do I need to run nova:publish after installing nova-gridder?
- Nova packages that ship compiled assets typically need them published, and republished after each deploy. Confirm the requirement for your Nova version and check whether the published bundle is committed or generated in your pipeline. Do not assume the asset pipeline is Vite-compatible on Nova 4 or later.
- What are alternatives to nova-gridder for custom Nova resource layouts?
- Nova's native panels and field grouping already cover a lot of layout density without an extra dependency. Gridder's component surface is small, essentially a layout wrapper plus slot rendering, so an in-house Nova field is a realistic option. Long term the native path is preferable; the package's value is layout ergonomics, and that is reproducible in a few hundred lines you own.
- Is it safe to use nova-gridder in production?
- The main risks are staleness and version coupling rather than security. It is presentation-layer only, with no authentication, no I/O and no data exposure beyond what Nova already renders. The real hazard is that a Nova upgrade breaks a package nobody is patching, so only ship it with a forked copy and a named owner.
- How do I test a Nova resource that uses nova-gridder?
- There is no evidence of a bundled test suite, so test at the application level: render the detail and form screens in a staging branch and assert the fields appear in the expected layout. Include responsive and dark-mode checks plus a production asset build to catch CSS purging problems. Because the package is version-sensitive, add an upgrade smoke test around every Nova version bump.