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

@wcstack/lint

v1.25.0

Published

Static-contract validator CLI (wcs-validate) for wcstack data-wcs bindings and wcstack.manifest.json sidecars. Thin npm wrapper around the wcstack-intellisense validator core.

Downloads

1,137

Readme

@wcstack/lint

🤖 AI coding agents: This README is a package-level reference, not the primary entry point for building a wcstack application. If you have not already done so, first read the repository README and AGENTS.md, then use the wcstack-app skill.

Static-contract validator CLI for wcstack: checks HTML data-wcs bindings and wcstack.manifest.json sidecars headlessly, with the same validator core as the WcStack IntelliSense VS Code extension — the IDE and this CLI report identical diagnostic codes and ranges.

日本語版 README はこちら

Usage

No install required:

npx @wcstack/lint --errors-only index.html wcstack.manifest.json

Or install and use the wcs-validate command:

npm i -D @wcstack/lint
npx wcs-validate --errors-only src/**/*.html

Files ending in .manifest.json are validated as sidecar manifests; everything else is validated as HTML with data-wcs bindings.

wcs-validate [--attr=data-wcs] [--state-tag=wcs-state] [--lang=ja|en] [--errors-only] <file> [<file> ...]

| Option | Description | |---|---| | --attr=<name> | Bind attribute name (default data-wcs) | | --state-tag=<name> | State custom-element tag name (default wcs-state) | | --lang=ja\|en | Diagnostic message language. Defaults to the environment locale (LC_ALL / LC_MESSAGES / LANG, then the OS locale); codes and ranges are language-independent | | --errors-only (alias --quiet) | Print only error-severity lines; warning/info counts and the exit code are unchanged |

Output & exit codes

One line per diagnostic, in a stable order:

index.html:12:8 warning wcs/path-nonexistent Path "user.nam" does not exist ...
app.manifest.json:1:3 error wcs/manifest-broken Broken manifest JSON: ...

1 error(s), 1 warning(s), 0 info

| Exit code | Meaning | |---|---| | 0 | No error-severity diagnostics (warnings/info may exist) | | 1 | At least one error-severity diagnostic | | 2 | Usage error or unreadable file |

Use in generate–validate–fix loops

Stable diagnostic codes, source:line:col ranges, and the exit-code contract make this CLI a drop-in gate for CI and for AI code-generation flows: generate HTML → npx @wcstack/lint --errors-only → read the diagnostics, fix, and re-run until exit code 0.

Relationship to the VS Code extension

This package is a thin distribution wrapper: it ships the self-contained CLI bundle built from the wcstack-intellisense validator core (zero runtime dependencies). The sidecar manifest is tooling-only and never changes runtime behavior; the normative schema lives in docs/wcstack-manifest-schema.md.

License

MIT