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

@fieldtest/registry

v1.0.2

Published

Schema registry for FieldTest SDK

Downloads

181

Readme

Fieldtest Registry

The Fieldtest Registry is a collection of schemas for common content types.

Running the Standard Schema Example

To run the Standard Schema example in this package, use the following commands from this directory:

# Compile the example to CommonJS JavaScript
tsc standard-schema.example.ts --module commonjs --esModuleInterop --outDir dist

# Run the compiled JavaScript with Node.js
node dist/standard-schema.example.js

You should see output like:

Success: hello world
Expected failure: Error: [
  {
    "message": "Must be a string"
  }
]

Note: Directly running the example with ts-node may fail due to ESM/CommonJS module system conflicts. Compiling first is the most reliable approach.

Running All Examples Easily

To run all Standard Schema example files and see a summary of results, use:

# Compile the runner script and run it
# (from this directory)
tsc run-examples.ts --module commonjs --esModuleInterop --outDir dist
node dist/run-examples.js

You'll see colorized output for each example and a summary at the end, e.g.:

[SUCCESS] standard-schema.example.ts
[SUCCESS] standard-schema-async.example.ts
[SUCCESS] standard-schema-missing-types.example.ts
[SUCCESS] standard-schema-bad-result.example.ts

Summary: 4 passed, 0 failed

This is the easiest way to check all example behaviors at once!