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

farcaster-in-three

v0.1.25

Published

A three-command tutorial for running your own Farcaster Snapchain node and client.

Readme

In Three

A three-command developer tutorial for running a Snapchain node and browser client from your own machine. Reads and writes go through your node, with no hosted Farcaster data API.

Website | Live proof | 中文教程 | npm | Docker | Source

The website includes a captioned 59-second walkthrough after the three-command quickstart.

What you need

  • a fresh Ubuntu or Debian operator machine; the install below can add Docker
  • an Ubuntu node machine with 4 CPU cores, 16 GB RAM, 2 TB free, SSH, and passwordless sudo
  • up to a day for the first sync

On macOS, install Docker Desktop first. If Docker is already available, the installer leaves it alone. npm and Node.js are not required for this path.

Use a machine you already own. Add --hetzner if you want In Three to create one.

You do not need a Farcaster account. It is handled in step 3.

  1. Create a Hetzner account and an empty project.
  2. In the project, open Security → API tokens. Generate a Read & Write token and copy it.
  3. On your account's Limits page, choose Request change → Limit increase. Request at least 2,048 GiB of total Volume storage.
  4. Run ./in-three-container provision --hetzner and paste the token when asked.

Hetzner reviews quota increases manually. See its official API-token guide and quota guide.

Install

mkdir in-three-node && cd in-three-node
curl -fsSLO https://raw.githubusercontent.com/P-U-C/farcaster-in-three/v0.1.25/in-three-container
chmod +x in-three-container
./in-three-container doctor --install-docker

On fresh Ubuntu or Debian, the last line installs and starts Docker. It does not install npm. Continue when the final line says All checks passed.

Run the three

./in-three-container provision
./in-three-container node up
./in-three-container client create
  1. Machine: enter the SSH address of a machine you own. Use ./in-three-container provision --hetzner instead to create one.
  2. Snapchain: starts your node. Leave it running during the first sync.
  3. Client: creates a test account or connects an existing one, then opens your client.

Keep the in-three-node folder. If setup pauses, rerun the same command from that folder.

For a scripted owned-machine setup, place a dedicated key in the working folder:

cp ~/.ssh/id_ed25519 ./node-key
./in-three-container provision --host [email protected] --ssh-key /work/node-key

Add --domain client.example.com when the SSH host is not the public client hostname.

Step 3 handles the Farcaster account

Choose CREATE, pick a password, and follow the funding prompt. In Three encrypts the new recovery phrase locally and sends only a revocable app key to the server.

Use a new test account. Never import a wallet that holds value.

When setup finishes, open the printed HTTPS URL and publish a test cast.

Useful commands

./in-three-container node status
./in-three-container client status
./in-three-container proof
./in-three-container destroy

node status checks all three shards. If it prints RECOVERY REQUIRED, run the exact ./in-three-container node recover --shard N command it shows. The recovery keeps healthy shards and verifies a fresh snapshot before a brief restart.

On Hetzner, destroy deletes the server and volume. On a machine you own, it stops In Three and keeps the machine and its data.

Prefer npm?

If Node.js 22+ and npm are already installed:

npm install --global farcaster-in-three
mkdir in-three-node && cd in-three-node
in-three doctor

Run the same three commands with in-three instead of ./in-three-container.

Help

Development

npm ci
npm run check
npm run build
node scripts/visual-check.mjs

Automated checks do not replace a complete mainnet sync, real account registration, public cast, and independent human test.

License

Original code and documentation are MIT licensed. Snapchain retains its upstream GPL-3.0 license.