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

@chrono-os/meresponda-core

v0.6.1

Published

Me Responda — schema (Zod) + motor de fluxo + registry de tipos de campo. Puro, sem dependências de framework; compartilhado entre o backend (NestJS) e o frontend (Next.js).

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

sugarhoneyiceteasugarhoneyicetea

Keywords

Readme

@chrono-os/meresponda-core

Contrato compartilhado do Me Responda (app de formulários): schemas Zod da estrutura do formulário, registry lógico de tipos de campo e o motor de fluxo puro.

É isomórfico e sem dependências de framework (só zod): o mesmo código roda no builder (preview), no renderer (avaliação client-side) e na API (revalidação server-side — fonte da verdade). Por isso este pacote não importa React nem nada de Node/Nest.

Instalação

yarn add @chrono-os/meresponda-core zod

zod é peerDependency (>=3) — o consumidor fixa a versão (^3.25).

O que exporta

  • Schemas (zod): formStructureSchema, blockSchema, fieldSchema, edgeSchema, conditionTreeSchema, answersSchema, themeSchema, formSettingsSchema.
  • Registry: fieldRegistry, getFieldType(id), FIELD_TYPE_IDS — cada tipo expõe configSchema, buildValueSchema(config), score?, toDisplay, capturesValue, canonical.
  • Motor (funções puras, nunca lançam):
    • nextBlock(structure, answers, currentBlockId, visitLog) — próximo bloco no grafo (guard de terminação).
    • evaluateCondition(structure, answers, condition, ctx?) — null = fallback; ref ausente ⇒ false (exceto isEmpty).
    • validateStructure(structure) — publish-time (edges válidos, alcançabilidade, keys únicas, repeater válido).
    • validateResponse(structure, answers, visitLog?) — valida só o caminho percorrido.
    • computeScore(structure, answers) — lead score + faixa.
    • extractCanonicalFields(structure, answers) — email/nome/telefone para o dashboard agregador.

Conceitos

  • FormStructure = documento JSONB versionado (blocks + edges/grafo). Bloco pode ter vários campos (pergunta composta) e repeat (repeater).
  • answers = Record<blockId, BlockAnswer>; bloco repeater = { kind:"repeater", activeCount, instances[] }.
  • Moeda em centavos (inteiro). Condições referenciam value da opção, nunca label.

Scripts

yarn build (tsup ESM+CJS+dts) · yarn test (Vitest) · yarn typecheck · yarn lint