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

janix

v0.2.4

Published

Isolated Docker + Nix dev environments per git branch

Downloads

535

Readme

janix

Janix creates isolated Docker + Nix dev environments per git branch. Each branch gets its own git clone, Docker container, and Nix-based environment — so you can work on multiple branches simultaneously without conflicts.

Each container mounts your Claude config, so Claude Code works inside environments out of the box.

How it works:

  • init configures the project: detects package manager, collects .env files, template variables, init/teardown scripts, and optional Docker network
  • create clones the repo for the branch, builds a Docker image from flake.nix, and starts a container with persistent cache volumes
  • attach drops you into an interactive shell inside the container via nix develop
  • Package manager and Nix caches are persisted across environment recreations via Docker volumes
  • flake.nix changes are detected automatically and trigger an image rebuild offer

Usage

janix init               # Initialize janix in current repo
janix create [branch]    # Create dev environment for a branch
janix list               # List environments and their status
janix attach [branch]    # Attach to a running environment
janix stop [branch]      # Stop a container (preserves clone)
janix start [branch]     # Start a stopped container
janix destroy [branch]   # Remove container and clone

Development

npm run check && npm run build