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

@joule-sh/code

v0.23.27

Published

An agentic coding terminal you can also drive from a web page.

Vulnerabilities

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

Links

Git

Maintainers

labidiaymenlabidiaymen

Keywords

agentclicodingterminaljoule

Readme

@joule-sh/code

An agentic coding terminal you can also drive from a web page.

npm i -g @joule-sh/code
joule

The command is joule, not code: code is already VS Code's CLI on most machines, and this would silently shadow or lose to it depending on PATH order. relay is installed alongside it, the same pair install.sh puts on your PATH.

What this package is

A wrapper. The binary itself lives in a per-platform package that npm installs as an optional dependency and skips everywhere it does not apply:

| platform | package | | --- | --- | | linux-x64 | @joule-sh/code-linux-x64 | | darwin-x64 | @joule-sh/code-darwin-x64 | | darwin-arm64 | @joule-sh/code-darwin-arm64 | | win32-x64 | @joule-sh/code-win32-x64 |

Every one of them carries the garbage collector it needs, so there is nothing to install alongside. The Linux binary is linked statically against musl and needs nothing at all from the machine it lands on.

If npm skipped the binary

npm has a long-standing bug where it fails to install the optional dependency it should have. The install step here falls back to fetching the platform package from the registry itself, so you should never see it. If you do, any of these fixes it:

npm install @joule-sh/code-linux-x64
rm -rf node_modules package-lock.json && npm install
JOULE_BINARY_PATH=/path/to/the/binaries joule

JOULE_BINARY_PATH takes a directory holding joule, relay and joule-daemon, or the path of one of them, and overrides resolution entirely.

Elsewhere