NextAdmin: a Next.js 16 template that lists Zod as an integration and does not depend on it

The integration list names Zod and the manifest does not have it

The page states which integrations are already wired up: TailGrids UI, Recharts, Leaflet, TanStack Table, Zod and FullCalendar. The dependency list tells a different story. FullCalendar, Leaflet with react-leaflet, Recharts and TanStack Table are all present, and TailGrids arrives through @tailgrids/icons with a tailgrids.config.json at the root, but there is no zod entry anywhere in the manifest. Meanwhile the actual list is much longer than six names, adding base-ui, floating-ui, dnd-kit, cmdk, sonner, embla-carousel, react-aria-components, internationalized date, date-fns, tailwind-merge, tailwind-scrollbar, next-themes and class-variance-authority. The practical lesson is about the page rather than the code: a feature list naming six integrations is not a dependency manifest, and a template is exactly the kind of project where that gap gets discovered at the moment you start writing validation. Getting the template onto your machine is the documented four-step path, which stops at a dev server on port 3000.

git clone https://github.com/NextAdminHQ/nextjs-admin-dashboard.git
cd nextjs-admin-dashboard

react-leaflet is pinned to a release candidate

One entry in the dependency list deserves a second look for anyone planning to build on this. react-leaflet is declared at ^5.0.0-rc.2, a release candidate, in a project whose whole purpose is to be cloned and relied on. A caret range on a pre-release is not the same guarantee as a caret range on a stable major, and the template is also on the React 19 line with react 19.2.4 and react-dom 19.2.4, where library compatibility is exactly the kind of thing that moves. The 1.2.1 entry in the changelog records fixing a peer dependency issue with React 19, and migrating from react-table to @tanstack/react-table, which is a reminder that this dependency set has already been through a major React transition once. If maps matter to your product, check that entry against the version you get rather than assuming the range will resolve cleanly.

There is no test script and no test directory

The scripts block has four entries: dev, build, start and lint. There is no test command, no coverage tool and no tests directory in the tree, which is normal for a template and worth stating plainly because of what the rest of the page promises. One of the shipped agent skills is specifically about keeping keyboard navigation, focus and ARIA attributes correct after an agent edits a component, and the 2.0.0 log credits the integration of a react-aria skill to enforce WCAG best practices. Those are conventions handed to an agent, not checks the project runs against itself. The 1.2.0 log shows the same intent in human terms, with dropdowns, modals and UI elements rebuilt using accessibility practices, and the 1.2.1 log fixing a reference error in one map component. Whether the accessibility claims hold after your changes is something you will have to verify yourself.

Auth was replaced once and the leftover file was renamed, not deleted

The 1.3.0 entry from May 2026 is the most useful line in the update log for anyone inheriting an older checkout. It replaced next-auth with better-auth, made authentication and authorization dynamic, added the Admin plugin from better-auth for role-based access control, and brought in two-step verification, email verification and password reset. It also replaced Algolia search with cmdk, moved utility files from libs into utils, reorganised environment variables and removed the unused ones, and renamed the unused proxy file to example.proxy.ts while fixing its import path. That last detail is the pattern to look for across the whole log: this project keeps dead files in place with an example prefix rather than removing them, which is friendly to a reader and a small hazard to a search. Three major versions, six dependency swaps and one library replacement in two years is a fast-moving base.

The community links point at a different brand name

The product calls itself NextAdmin and lives under the NextAdminHQ GitHub organisation, but the community section links to a Discord at pimjo.com/community and an X account at twitter.com/PimjoHQ. The GitHub link is the only one that matches the project name. That is not a defect in itself, since products get renamed, and the demo, docs, components, AI and pricing pages all sit under the nextadmin.co domain as expected. It does mean a search for community support will land you somewhere other than the name on the repository. The other detail in this section is the licensing position: the page describes NextAdmin as a free, open-source admin dashboard, and the tree at the root contains no LICENSE file. The free edition covers most of what is needed to get a dashboard running, while the Pro edition at nextadmin.co/pricing adds the full component set, extra dashboards and the Figma source.

The mock REST APIs are the seam the api-integration skill pulls on

Every page in the template is interactive and connected to mock REST APIs shaped the way a real API would be, and that is the design decision worth understanding before you edit anything. The pages are not static mockups with hardcoded arrays; they exercise a request and response cycle, which means the loading states, error paths and skeletons you see are real code you keep. The 2.0.0 log records making all pages interactive this way, and 1.2.0 added API integration with loading skeletons for tables and charts. Against that arrangement the api-integration skill is the escape hatch, swapping mock data for your live endpoints from a single prompt. Two other seams sit alongside it: a Figma design source for rearranging before touching code, and dark and light mode with the colours checked on both. Removing the mocks is therefore the last step of adoption rather than the first.

The AI-first pitch is four directories and a file at the root

The differentiating claim is that an agent can read the project and build features that match its patterns instead of inventing its own, and the mechanism is visible in the tree. AGENTS.md sits at the root next to CLAUDE.md, there is a .agents/ directory, and prompts/ holds the custom prompts the page describes as covering core setup, layout, UI and auth. Four things are named as agent-facing: Agent Skills that give the agent the full picture of the components, design system and file structure so it does not start from zero, React Aria skills for keyboard, focus and ARIA correctness after edits, the api-integration skill for swapping mocks, and the custom prompts. The reasoning behind the pitch is the failure mode it names, that on a second and third session an agent picks a different folder layout, a different auth approach and slightly different styling, and you end up fixing patterns instead of shipping features. Docs live off-repository with machine-readable context files alongside them.

Three Next.js jumps in one year and a patch release that upgraded everything

The update logs read like a maintenance history worth reading before you pin anything. Version 1.0.0 and 1.1.0 arrived in 2024, 1.2.0 moved to Next.js v15 in January 2025, 1.2.2 moved to Next.js 16 in December 2025, 1.2.3 pinned ^16.1.6 and configured image qualities in March 2026, 1.3.0 in May 2026 rewrote authentication, and 2.0.0 landed on July 20, 2026 with the redesign and the agent skills. The manifest now pins next 16.2.7. Two oddities are worth noting. A patch number, 1.2.2, carries a framework major upgrade, and 1.2.3 carries a dependency pin and image quality configuration, so the patch level is not a safe place to expect small changes. And the sequence skips a 1.2.4 and a 1.2.0-to-1.2.1 gap of three months, which means the numbers track marketing rather than compatibility guarantees. The last commit on the default branch is dated 2026-08-18.

Editorial conclusion

NextAdmin is a good fit when you want a dashboard that already has decided its component set, its auth approach and its data shape, because that is the exact problem the template sells itself against and the reason the agent-facing files exist. Two things to check before you commit. The advertised integration list does not match the manifest, with Zod named on the page and absent from the dependencies, so treat the feature list as marketing and the manifest as the truth. And there is no test script and no test directory, so the accessibility work the react-aria skill describes is convention rather than enforcement. If you are starting from an empty repository, the paid edition is where the extra dashboards and the Figma source live; if you only need the free component set, this is a reasonable place to start. Read the update logs before you pin a version, since the Next.js line moved three times in a year.

Frequently asked questions

Official sources

1. Issues
2. NextAdminHQ/nextjs-admin-dashboard on GitHub
3. Project website
4. README