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

@stndrds/client

v1.0.0-alpha.381

Published

Public TypeScript client for Standards: declare schema sources with the fluent builders, sync them to a hosted tenant, and operate typed records over the REST API.

Readme

@stndrds/client

Declare your schema with the @stndrds/schema fluent builders, sync it to a hosted Standards tenant, and operate typed records — from any Node ≥ 22 server process. No runtime, no NestJS.

pnpm add @stndrds/client

Everything you need — the builders, createStandards, defineSchemaSource, error classes — is exported from @stndrds/client. One package, one version.

1. Declare a source

import { date, defineSchemaSource, object, select, text } from "@stndrds/client";

export const incident = object("incidents", "Incident")
  .attribute(text("title", "Title").required())
  .attribute(
    select("severity", "Severity").options([
      { value: "minor", label: "Minor" },
      { value: "major", label: "Major" },
      { value: "critical", label: "Critical" },
    ])
  )
  .attribute(date("startedAt", "Started at"))
  .labelExpression("{{ title }}");

export const statusSource = defineSchemaSource({ id: "status-site", objects: [incident] });

2. Sync it (server-side only)

import { createStandards } from "@stndrds/client";

// Reads STANDARDS_API_URL and STANDARDS_API_KEY (explicit { baseUrl, apiKey } win).
// Create the key with a role granting architect:update (`standards keys create --role`); keys default to member.
const standards = createStandards();

const result = await standards.schema.sync(statusSource);
// { applied: false, hash } when nothing changed — one GET, no write.

Objects you push are system: users can add their own attributes and views on top, but cannot delete or retype yours. Remove an object from the source and it is demoted to a custom object — its records survive. Never call createStandards with an API key in browser code; it refuses to.

3. Typed records

const db = createStandards({ baseUrl, apiKey, schema: statusSource });
const incidents = db.incidents; // one typed query per object, keyed by the camelCase of its name

await incidents.create({ title: "API latency", severity: "major", startedAt: new Date() });
const critical = await incidents.eq("severity", "critical").orderBy("startedAt", "desc").limit(10).fetch();

Inputs are typed from the builder (severity only accepts the three options); dates come back as Date.

Errors

StandardsAuthError (401/403), SchemaSourceConflictError (409 from schema.sync, with objectName and owner), SchemaSourceValidationError (400 from schema.sync, server message verbatim), StandardsRequestError (any other non-2xx, with the server's code), StandardsConfigurationError (misuse). schema.sync never throws for "nothing to do".

Licensed under the Standards SDK License 1.0 — see LICENSE. This package is not open source: it is provided to build applications that communicate with Standards.