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

@dynui/cli

v0.1.0

Published

Small, file-based developer CLI for DynUI: validate and lint component manifests, and print JSON Schemas. Not a management console.

Downloads

147

Readme

@dynui/cli

A small, file-based developer CLI. It wraps the same public functions you'd call in code, so a project can validate and lint manifests — and read the shipped JSON Schemas — without writing TypeScript. It is deliberately not a management console: no network, no state, no config.

npx @dynui/cli validate manifest.json            # parse + schema-validate a manifest
npx @dynui/cli validate-tree tree.json m.json    # STRUCTURAL UITree validation
npx @dynui/cli lint manifest.json                # governance lint (non-zero on errors)
npx @dynui/cli schema component-manifest         # print a shipped JSON Schema
npx @dynui/cli schema                            # list available schemas
npx @dynui/cli --help

Once installed as a dependency, the binary is named dynui (e.g. dynui validate manifest.json). In this repo you can also run it via npm run dynui -- <args>.

Commands

| Command | What it does | |---------|--------------| | validate <manifest.json> | Parses the manifest with the runtime schema (parseComponentManifest) and reports [code] path: message issues. Exit 1 on failure. | | validate-tree <tree.json> <manifest.json> | Parses a UITree and runs structural validation (validateTreeStructure). This is not the render gate — full validation needs request context (consent, data, surface, experiments); use validateRenderableTree(...) in code. | | lint <manifest.json> | Governance lint (lintManifest): missing descriptions/contracts/goals, ambiguous variants, wildcard audiences, deprecations. Exit 1 on errors (warnings don't fail). | | schema [<artifact>] | Prints a JSON Schema shipped with @dynui/contracts (component-manifest, signal-profile, ui-tree, generation-request, behavior-event, experiment-def, signal-model). No arg lists them. |

What this CLI is not

Running contract/generation evals and checking JSON-Schema freshness are framework-repo tasks (npm run eval:contracts, npm run eval:generation, npm run gen:schema -- --check) — see CONTRIBUTING.md. They operate on the framework's own source, not on an adopter's project, so they're npm scripts rather than CLI commands.