npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@voyantjs/legal-react

v0.119.2

Published

The legal client tier: headless data hooks/clients plus the styled UI components and page-level compositions (formerly `@voyantjs/legal-ui`).

Downloads

19,629

Readme

@voyantjs/legal-react

The legal client tier: headless data hooks/clients plus the styled UI components and page-level compositions (formerly @voyantjs/legal-ui).

Headless consumers (storefronts, portals) import from the root, ./hooks, ./client, or ./query-keys — these pull no styling peers. Styled surfaces live under ./ui, ./components/*, ./admin, ./i18n, and ./styles.css, whose heavier peers (@voyantjs/ui, @voyantjs/admin, react-hook-form, and the other modules' *-react/*-ui packages) are optional and only needed when you import those subpaths.

Install

pnpm add @voyantjs/legal-react @voyantjs/ui @tanstack/react-query react react-dom

@voyantjs/ui provides the design-system primitives for the styled subpaths. The data-layer hooks ship from this package's root.

All components accept a className prop and merge it with cn(). Wrap or compose to extend; use the registry copy-paste path (npx shadcn add @voyant/...) for components you want to fork outright.

Detail Tab Replacement Slots

ContractDetailPage exposes slots for replacing built-in tab content while keeping the default tab navigation. Use detailsContent, partiesContent, signaturesContent, or documentsContent when an app needs custom inline management controls instead of the shipped read-only table.

Contract Dialog

ContractDialog provides the default create/edit form for ContractsPage and ContractDetailPage. It owns contract setup, template and version selection, number series, expiry, template variables, additional variables, metadata, and submit wiring. Linked record pickers stay optional render props so apps can wire CRM, supplier, or distribution selectors without the styled tier taking those runtime dependencies.

import { ContractDialog, ContractsPage } from "@voyantjs/legal-react/ui"

<ContractsPage
  renderContractDialog={(props) => (
    <ContractDialog
      {...props}
      renderPersonPicker={(pickerProps) => <PersonPicker {...pickerProps} />}
      renderOrganizationPicker={(pickerProps) => <OrganizationPicker {...pickerProps} />}
    />
  )}
/>

I18n

Components render English by default. To localize them, wrap your UI in LegalUiMessagesProvider and import only the locales your app supports.

import { LegalUiMessagesProvider } from "@voyantjs/legal-react/ui"
import { legalUiEn } from "@voyantjs/legal-react/i18n/en"
import { legalUiRo } from "@voyantjs/legal-react/i18n/ro"

English-only apps should import only ./i18n/en. Bilingual apps can import ./i18n/en and ./i18n/ro.