FAQ
Common questions about scope, compatibility, and what's planned.
Is Prism a component library?
No. Prism's own Layer 1 primitives exist to give the form engine something concrete to wire up, and the CLI installs them so you have a working starting point, but they're not meant to compete with shadcn/ui, Radix, or Material UI. You can wrap any UI library's components in a Prism field component, see Custom Fields.
Why is the npm package @prismrepo/cli but the command is prismrepo?
The unscoped name prism-ui was already taken on npm by an unrelated package. The npm package
was renamed to the scoped @prismrepo/cli to resolve the conflict; the command users actually
type, prismrepo, is unaffected, see the package's own bin field in
CLI Commands.
Does Prism work with Formik or TanStack Form?
Not in the current release. React Hook Form is the only supported form-library integration.
Does Prism work with a validation library other than Zod?
Not in the current release. Zod is the only supported validation integration, via
@prismrepo/adapter-zod.
Does Zod 3 work?
No. @prismrepo/adapter-zod requires Zod ^4.0.0, see
Zod Adapter.
Is PrismProvider required?
No. usePrismForm takes a FormDefinition that already carries its own registry, forms work
with no PrismProvider in the tree at all. PrismProvider is for when you want a registry
available ambiently across part of your tree, see
@prismrepo/react.
Does Prism support React 18?
Yes, ^18.0.0 || ^19.0.0 across every package that declares react as a peer dependency, see
Requirements.
Is there a data grid, table, or dashboard package?
Not yet. Prism's current product milestone is forms only. Tables/data grids, an API integration layer, a CRUD engine, permissions, dashboards, workflows, and file management are long-term directions that inform today's package boundaries but are explicitly out of scope until the forms milestone is further along.
Where do I report a bug or ask a question?
Open an issue on GitHub.