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

devportal-tunnel

v1.0.1

Published

Expose your localhost to the internet with a single command

Readme

DevPortal CLI

Expose your localhost to the internet with a single command.

Installation

From npm (after publishing)

npm install -g devportal

From source

git clone <repo>
cd cli
npm install
npm run build
npm link

Quick Start

# Expose port 3000
devportal 3000

# With custom subdomain
devportal 3000 --subdomain my-api

# Password protected
devportal 3000 --password secret123

# Show QR code for mobile testing
devportal 3000 --qr

# Temporary demo link (expires in 2 hours)
devportal 3000 --demo

# Run in local simulation mode (no server needed)
devportal 3000 --local

Commands

Start a tunnel

devportal <port> [options]

Options:
  -s, --subdomain <name>    Custom subdomain for your URL
  -p, --password <pass>     Password protect the tunnel
  --demo                    Create a temporary link (2 hours)
  --qr                      Display QR code in terminal
  --auth-header <header>    Add authorization header to forwarded requests
  --local                   Run in simulation mode (no server required)

List active tunnels

devportal ls

Stop a tunnel

# Stop specific tunnel
devportal stop <tunnel-id>

# Stop all tunnels
devportal stop --all

Replay requests

# Replay a captured request
devportal replay <request-id>

# With modified headers
devportal replay <request-id> --header "X-Debug: true"

# With modified body
devportal replay <request-id> --body '{"test": true}'

Stream logs

devportal logs <tunnel-id>

Configuration

# View current config
devportal config

# Set server URL (for self-hosted)
devportal config server https://your-server.com

# Reset to defaults
devportal config reset

Device info

devportal whoami

Configuration

DevPortal stores configuration in ~/.devportal/:

~/.devportal/
├── config.json     # Server URL, WebSocket URL
├── device.json     # Unique device ID
└── tunnels.json    # Active tunnel information

Self-Hosted Server

To use your own DevPortal server:

# Set your server URL
devportal config server https://tunnel.your-domain.com

# Now tunnels will use your server
devportal 3000

How It Works

  1. CLI connects to the DevPortal server via WebSocket
  2. Server assigns a public URL (e.g., https://my-app.devportal.live)
  3. Requests arrive at the public URL
  4. Server forwards requests through the WebSocket to CLI
  5. CLI proxies requests to your local server
  6. Response travels back through the tunnel
Internet Request
      │
      ▼
[DevPortal Server] ◄──WSS──► [CLI Client] ──► [localhost:3000]
      │                            │
      └──────── Response ◄─────────┘

Publishing to npm

  1. Update package.json with your details:
{
  "name": "devportal",
  "author": "Your Name",
  "repository": {
    "type": "git",
    "url": "https://github.com/yourusername/devportal"
  }
}
  1. Login and publish:
npm login
npm publish
  1. For scoped package (if name is taken):
{
  "name": "@yourusername/devportal"
}
npm publish --access public

Development

# Install dependencies
npm install

# Run in development
npm run dev 3000

# Build
npm run build

# Link globally for testing
npm link

License

MIT