Installation
Astronaut CMS requires Node.js 26, Astro 7 and React 19.
Install the CMS package along with its peer dependencies.
vite is a peer too, but Astro already depends on it, so it needs no install of its own.
sh npm install astronaut-cms @astrojs/react react react-dom zod
sh pnpm add astronaut-cms @astrojs/react react react-dom zod
Peer Dependencies
Section titled “Peer Dependencies”| Package | Version | Purpose |
|---|---|---|
astro |
^7 |
Astro framework |
@astrojs/react |
^7 |
React integration for the admin panel |
react |
^19 |
React runtime |
react-dom |
^19 |
React DOM renderer |
vite |
^8 |
Shared with Astro, loads your configs |
zod |
^4 |
Collection and component schemas |
Optional Dependencies
Section titled “Optional Dependencies”| Package | Version | Purpose |
|---|---|---|
@astrojs/mdx |
^7 || ^8 |
MDX support for block components |
The admin ships compiled with its dependencies, stylesheet included, so the CMS adds no Tailwind plugin to your build and nothing but the peers above to your lockfile.
Testing a local build
Section titled “Testing a local build”Try an unreleased build as a tarball rather than a file: dependency.
A file: link resolves astro, react, zod and vite from the CMS checkout’s own node_modules, and two copies of zod make every defineComponent a type error.
# in the astronaut-cms checkoutnpm pack# in your sitenpm install ../astronaut-cms/astronaut-cms-0.0.0.tgzRun that install again, with the path, after every npm pack.
The version stays the same, so a plain npm install keeps the previous tarball, whose integrity the lockfile pinned.
An .npmrc that disables file: dependencies with allow-directory=none style settings refuses the tarball as well.
Add allow-file=all to your site’s .npmrc for the install.
