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

@surveystudio/node-registery

v1.14.12

Published

Typed survey question node registry with split builder, runner, and logic entrypoints.

Readme

@surveystudio/node-registery

Typed survey question node registry with separate entrypoints for pure logic, runner UI, and builder UI.

This package is currently in early migration. It exports migrated node logic for server runtimes and selected builder/runner UI adapters while the remaining SurveyChamp question nodes are being moved into the registry.

Entrypoints

import { logicRegistry } from "@surveystudio/node-registery/logic";
import { runnerRegistry } from "@surveystudio/node-registery/runner";
import { builderRegistry } from "@surveystudio/node-registery/builder";
import { TextLikeNode, ChoiceNode } from "@surveystudio/node-registery/ui";

Use /logic for Worker, export, and server runtimes. It is intentionally React-free.

Use /runner, /builder, and /ui only in React runtimes. React is a peer dependency and is not bundled. The /ui entrypoint contains shadcn-style primitive parts for node UIs; Worker and API runtimes should keep importing only /logic.

Builder manifests/adapters are available for the migrated input, choice, scale, structured choice, consent, media, flow, captcha, emoji rating, and plain text nodes.

Logic Pipeline

Every node logic module should expose the same pure, Worker-safe pipeline:

const value = logicRegistry.plainText.normalizeValue(rawAnswer, node.data, context);
const validation = logicRegistry.plainText.validate(value, node.data, context);
const columns = logicRegistry.plainText.extractValue(value, node.data, context);

Runner APIs should persist and queue normalized values. Export/projection APIs should read normalized values through extractValue.

Current Status

Migrated nodes:

  • textInput
  • numberInput
  • emailInput
  • dateInput
  • multiInput
  • zipCodeInput
  • singleChoice logic
  • multipleChoice logic
  • dropdown logic
  • ranking logic
  • matrixChoice logic
  • cascadingChoice logic
  • rating logic
  • slider logic
  • consent logic
  • captcha logic
  • image logic
  • video logic
  • audio logic
  • plainText
  • emojiRating logic
  • start logic
  • end logic
  • branch logic
  • validation logic

The registry contract test covers every migrated logic and builder node so package consumers fail fast if an entrypoint goes stale.