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 🙏

© 2025 – Pkg Stats / Ryan Hefner

jjjj-cli

v1.0.11

Published

A Stacked PR tool sitting atop Jujutsu VCS with GitHub integration

Readme

JJJJ

A Stacked PR tool sitting atop Jujutsu VCS.

jjjj introduces a bunch of commands related to stacked PRs workflow, which will pass-through any commands directly to jj for simplicity.

Requirements

Installation

npm install -g jjjj-cli

This installs the j command globally. You can verify with j --help.

Development Installation

If you want to contribute or run from source:

git clone https://github.com/dacuha-ic/jjjj.git
cd jjjj
npm install
npm run dev:install

This builds locally and installs a shim to ~/.local/bin/j.

How does a normal workflow look like?

$ j new -m foo
$ touch foo
$ j new -m bar
$ touch bar

# Creates bookmarks and pushes to Github
$ j sync
# Mark all PRs up until to the current point as ready
$ j ready

Demo video

https://github.com/user-attachments/assets/8cbb6736-c486-4181-9deb-27069db5c7e3

Main commands

NOTE: anything outside of this list will simply passthrough to JJ, so you can use j for anything jj too!

sync

Creates bookmarks (if needed) and pushes to Github. It will use {yourUsername}/{revId}/your-revision-descriptions-first-line. It will additionally strip any conventional commit prefixes (e.g.: 'feat: some fancy feature' -> 'some-fancy-feature')

restack

Does a jj git fetch, followed by rebases for the whole current stack. You can pass --all to restack ALL the stacks to latest.

stack

jj log equivalent but only displays the current stack.

ready

Marks all PR up to the current point as ready

merge

VERY EXPERIMENTAL. Merges the stack's PRs up to the current point. It will wait until each PR is mergeable, approved, etc. then merge, restack and sync.

top | bot | prev | next

Navigational commands to move through the stack

desc

Describes the current revision, a shorthand for jj describe, but instead of opening an editor, it just prompts for a commit description, enter to submit.

aidesc

Lets AI describe the current revision, with a picker of the changed files to send specific diffs over to OpenAI's API.

clean

Removes any dangling empty, mutable revisions.

pull

Pulls an existing branch from origin, useful for checking out code from other people.

Config

You can create a .jjjjrc.json file in your home directory or within ~/.config/.jjjjrc.json. A config file is not required for now.

  • openAIApiKey only needed for aidesc
  • openAIBaseURL if you use anything like a proxy to reach OpenAI's API.
  • githubToken if you pass this, jjjj will use this for any github operations, otherwise it will fall back to use gh auth token