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

@nocios/frontend-types

v1.0.0

Published

Canonical frontend type contracts for the CRUDIFY monorepo

Downloads

12

Readme

@nocios/frontend-types

Canonical frontend type contracts for the CRUDIFY monorepo.

Purpose

This package centralizes shared type definitions across frontend workspaces:

  • domain models (actions, modules, policies, forms),
  • frontend API contracts (core CRUDIFY and admin),
  • shared utility contracts (filters, sort, pagination, populate),
  • tenant configuration model.

This package is intentionally type-focused. It does not contain runtime business logic.

Scope of v1

  • Canonical shared types only.
  • No legacy alias layer.
  • No consumer migration performed in this phase.
  • No local UI-only types from each app unless they are truly shared contracts.

Canonical Domains (v1)

  • domain/action: action definitions, view/position enums, list/form/custom payload contracts.
  • domain/module: module schemas, module definitions, and module version history.
  • domain/policy: policy field permissions and required permission contracts.
  • domain/form: form field kinds, dynamic values, computed values, and password rules.
  • contracts/crudify-core: shared CRUDIFY request/response and transaction contracts.
  • contracts/crudify-admin: admin API envelopes, filters, and create/edit inputs.
  • contracts/tenant: tenant and frontend environment contracts.
  • shared/common: shared low-level filter/sort/pagination/populate primitives.

Canonical Source Rule

When existing types conflict, API/backend contract has precedence.

Public API

Imports are available from:

  • @nocios/frontend-types
  • @nocios/frontend-types/domain
  • @nocios/frontend-types/contracts
  • @nocios/frontend-types/shared

Documentation

Development

pnpm --filter @nocios/frontend-types run typecheck
pnpm --filter @nocios/frontend-types run lint
pnpm --filter @nocios/frontend-types run test
pnpm --filter @nocios/frontend-types run test:coverage

Versioning Policy

  • Breaking public type changes require a major version bump.
  • Additive backward-compatible type changes require a minor version bump.
  • Fix-only type corrections (without breaking consumers) require a patch bump.

Notes

  • Package is published as @nocios/frontend-types in npm for shared type consumption.
  • Publish flow is manual and controlled (next -> validation -> latest).
  • npm credentials must be provided via NPM_TOKEN environment variable only.
  • A source-to-canonical mapping matrix lives in docs/source-to-canonical-matrix.md.
  • v1 intentionally excludes legacy aliases and consumer migration work.