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/joy

v0.0.2

Published

The Joy platform for browser apps in WebAssembly, and the joy-html package its views are written in: the Elm architecture, effects as data, subscriptions, typed HTML and server rendering.

Downloads

389

Readme

@roc-syntax/joy

A roc-syntax-mcp plugin: the corpus of the Joy platform and of joy-html, the package its views are written in. A model that writes a Joy app reads the platform and the HTML types that the app compiles against, and does not recall them.

No JavaScript runs from this package. It is Roc source, prose and a manifest.

Install

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

Then restart your AI harness. The server serves the plugin in every workspace. To serve it from one client entry only, start the server with --plugin=@roc-syntax/joy, or set ROC_MCP_PLUGINS=@roc-syntax/joy.

When the server detects an app header that pins a joy release, it adds the joy scope to the default working set. Before there is a header, get_roc_syntax() lists joy as "web apps in the browser" beside the bundled platforms. joy-html is a documented package: an app that pins it gets its signatures, and any platform's app can pin it.

What it serves

| Part | Is | |---|---| | joy-overview.md | What get_roc_syntax(scope: "joy") returns: how a project is started and built, the app contract, effects and subscriptions, HTTP, time, ports, testing and the traps | | html-overview.md | What get_roc_syntax(topic: "joy-html") returns: element shapes, attributes, events, lazy regions and server rendering | | index.json | Both releases' own modules, parsed by plugin index. No source is vendored | | examples/ | Complete programs from joy, all of which type-check | | topics/ | Programs get_roc_syntax(topic:) answers with: joy_app, joy_http, joy_subscriptions, html_views, html_ssr | | scaffold.roc | The app roc_check wraps bare source in, with joy-html imported |

Pinned to

The two releases in plugin.json, and the nightly its compiler line names. UPSTREAM records the commits, the tarball hashes and the upstream files that this package does not include.

License

Apache-2.0, as both upstream repositories are. LICENSE is an exact copy of upstream's. The manifest, the overview pages and the topic files are this package's own, under the same license.

Changed files, as Apache-2.0 section 4(b) asks: every file in examples/ is joy's, with one line changed. Upstream's platform pin is a relative path to the platform in joy's own repository. This copy pins the release URL. UPSTREAM records the commit that the files came from.