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

hurler

v0.10.1

Published

A GUI for managing and running [Hurl](https://hurl.dev) HTTP request collections.

Readme

Hurler

A GUI for managing and running Hurl HTTP request collections.

Run npx hurler in any project directory to get a web-based interface for organizing .hurl files, managing environments, and executing requests.

Quick Start

npx hurler

This starts a local server at http://localhost:4000 and stores data in a .hurl/ directory in your current working directory.

Prerequisites

Usage

npx hurler [options]

Options

| Flag | Description | |---|---| | --port, -p | Port to run the server on (default: 4000) | | --open, -o | Open the browser automatically |

You can also set the port via the PORT environment variable.

Examples

npx hurler                  # start on port 4000
npx hurler -p 8080          # start on port 8080
npx hurler -o               # start and open browser
npx hurler -p 8080 -o       # combine flags

Data Storage

All data is stored in .hurl/ relative to where you run the command:

.hurl/
├── collections/    # .hurl request files
├── environments/   # environment variable files
└── metadata.json   # UI organization (sections, groups)

This directory is safe to commit to version control if you want to share collections with your team.

Environments

Hurler supports two types of environment files:

| File | Purpose | Commit to Git? | |------|---------|----------------| | {name}.env | Non-sensitive variables (URLs, feature flags, etc.) | ✅ Yes | | {name}.secrets.env | Sensitive values (API keys, tokens, passwords) | ❌ No |

Both files are automatically merged when running requests. Variables from either file can be used in your .hurl files with {{variable}} syntax.

Gitignore Setup

Add this to your .gitignore to keep secrets out of version control:

# Hurler secrets
.hurl/environments/*.secrets.env

Example

# .hurl/environments/dev.env (safe to commit)
base_url=https://api.dev.example.com
timeout=30

# .hurl/environments/dev.secrets.env (gitignored)
api_key=sk-abc123...
auth_token=bearer-xyz...

Then use in your .hurl files:

GET {{base_url}}/users
Authorization: Bearer {{auth_token}}

License

MIT