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

wopr-plugin-tailscale-funnel

v1.0.0

Published

Expose WOPR services externally via Tailscale Funnel

Readme

wopr-plugin-tailscale-funnel

Expose WOPR services to the internet via Tailscale Funnel.

Note: Tailscale Funnel only supports one port at a time. Exposing a new port will automatically stop the previous funnel.

Prerequisites

Installation

wopr plugin add wopr-network/wopr-plugin-tailscale-funnel

Configuration

In your WOPR config (~/.wopr/config.json):

{
  "plugins": {
    "wopr-plugin-tailscale-funnel": {
      "enabled": true,
      "expose": { "port": 7437, "path": "/" }
    }
  }
}

Options

| Option | Type | Default | Description | |--------|------|---------|-------------| | enabled | boolean | true | Enable/disable the plugin | | expose | object | - | Port to auto-expose on startup (one port only) |

CLI Commands

# Check funnel status
wopr funnel status

# Expose a port (replaces any existing funnel)
wopr funnel expose 8080

# Stop exposing a port
wopr funnel unexpose 8080

Extension API

Other plugins can use the funnel extension:

const funnel = ctx.getExtension("funnel") as FunnelExtension;

// Check availability
const available = await funnel.isAvailable();

// Get public hostname
const hostname = await funnel.getHostname();

// Expose a port and get public URL (replaces any existing funnel)
const url = await funnel.expose(8080, "/api");

// Stop exposing
await funnel.unexpose(8080);

// Get URL for the currently exposed port
const existingUrl = funnel.getUrl(8080);

// Get full status
const status = funnel.getStatus();

How It Works

  1. Plugin checks if Tailscale is installed and connected
  2. When exposing a port, it runs tailscale funnel <port> in the background
  3. Traffic to https://<your-hostname>.ts.net/ routes to localhost:<port>
  4. Other plugins (like wopr-plugin-github) can use the extension to get public URLs
  5. Only one funnel can be active - exposing a new port stops the previous one

Limitations

  • Single port only: Tailscale Funnel supports one exposed port at a time per machine
  • Exposing a new port will automatically stop any existing funnel

Operational Notes

Tailscale Must Be Running First

Tailscale daemon (tailscaled) must be running before WOPR starts. In containerized environments:

# Ensure tailscale is up
tailscale up --authkey=<your-key>

# Clear any conflicting listeners before starting funnel
tailscale serve reset

# Then start WOPR
wopr daemon

Container Setup

For Docker containers, run in privileged mode and ensure Tailscale auto-starts:

# In your entrypoint
tailscaled --state=/var/lib/tailscale/tailscaled.state &
sleep 2
tailscale up --authkey=${TAILSCALE_AUTHKEY}

Troubleshooting

  • "listener already exists": Run tailscale serve reset to clear existing funnels
  • Funnel not accessible: Verify funnel is enabled on your tailnet in the admin console
  • Port not exposed: Check tailscale funnel status for current state

License

MIT