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

staklink

v0.4.11

Published

staklink process manager

Readme

staklink

VSCode extension for automating development and debugging in Codespaces.

CLI

npx -y staklink@latest start

local cli testing

pm2 stop all
pm2 delete all
pm2 flush
rm ~/.pm2/logs/*.log

yarn build:cli
yarn build:proxy

node bin/staklink.cjs start

processes

There are 2 ways to configure your dev processes (like your backend, frontend, db, etc)

pm2

In your .devcontainer folder, add a pm2.config.js file. This can be used to manage your dev processes using pm2.

For example:

module.exports = {
  apps: [
    {
      name: "sphinx-tribes-backend",
      script: "./sphinx-tribes",
      cwd: "/workspaces/sphinx-tribes",
      instances: 1,
      autorestart: true,
      watch: false,
      max_memory_restart: "1G",
      env: {
        RESTART: "true",
        REBUILD_COMMAND: "go build -o sphinx-tribes",
        POST_RUN_COMMAND: "./seed-dummy-data.sh",
      },
    },
    {
      name: "sphinx-tribes-frontend",
      script: "npm",
      args: "run start:codespace",
      cwd: "/workspaces/sphinx-tribes-frontend",
      instances: 1,
      autorestart: true,
      watch: false,
      max_memory_restart: "1G",
      env: {
        NODE_ENV: "development",
        INSTALL_COMMAND: "yarn install",
      },
    },
  ],
};

The above config runs the backend and the frontend. In the env section:

  • RESTART: will make the service rebuild and restart if needed (when code is updated)
  • REBUILD_COMMAND: a custom "rebuild" command
  • INSTALL_COMMAND: a custom dependency installation step
  • POST_RUN_COMMAND: arbitrary command to run after a service starts (such as seeding DB with dummy data)
  • PORT: port number, to let external workflows know which port maps to which service

docker-compose.yml

In your .devcontainer folder, add a docker-compose.yml file. This can be used to manage long-running processes that don't need to be controlled, rebuilt, or customized (like a database)

For example:

version: "3.8"

volumes:
  postgres-data:

services:
  app:
    build:
      context: .
      dockerfile: Dockerfile
    env_file:
      - .env

    volumes:
      - ../..:/workspaces:cached

    # Overrides default command so things don't shut down after the process ends.
    command: sleep infinity

  db:
    image: postgres:latest
    restart: unless-stopped
    volumes:
      - postgres-data:/var/lib/postgresql/data
    env_file:
      - .env

This config runs the dev container (app), and the backend database (db).