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

@roc-syntax/weaver

v0.0.2

Published

The Weaver command-line argument parser, as a roc-syntax-mcp corpus.

Readme

@roc-syntax/weaver

The Weaver command-line argument parser, as a corpus roc-syntax-mcp can serve: the package's public modules, its worked examples, topic programs written against the release, and an overview page on which every claim was compiled.

Weaver is a package rather than a platform, so this plugin adds no scope. It serves the lukewilliamboswell/weaver namespace. When an app's header pins weaver, a search covers weaver's names together with the builtins. The page, topics and examples answer even before any app pins weaver.

roc-syntax-mcp plugin add @roc-syntax/weaver

Then get_roc_syntax(topic: "weaver") for the page, get_roc_syntax(topic: "weaver_cli") for a complete program, search_symbols Opt.flag for one signature.

| Path | Is | |---|---| | index.json | The release's own modules, parsed by plugin index. No source is vendored | | examples/ | Upstream's examples, repinned to the release tarball and moved onto the basic-cli this server bundles | | topics/ | Five programs written for this corpus, answerable by name | | verify/ | Every snippet the overview shows, compiled as one app | | overview.md | What get_roc_syntax(topic: "weaver") returns | | UPSTREAM | What was vendored, from where, and what was changed |

Weaver is UPL-1.0 from 0.9.1, and so is this package. LICENSE says whose copyright each file carries.

Checked with roc-syntax-mcp plugin validate . against the nightly the compiler line in plugin.json names.