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

@talesmgodois/trex

v0.2.3

Published

Terminal-based tool for HTTP requests (Trex)

Downloads

500

Readme

trex

Install

bun install

Run

Trex starts a small CLI from src/index.ts.

Examples:

# list registered requests/functions (from config)
bun run ./src/index.ts list

# execute a request by name
bun run ./src/index.ts req getTodo

# run with a jq filter (jq syntax)
bun run ./src/index.ts req getTodo --filter .title

Configuration (trex.config.ts)

Trex loads a config file on startup and executes it once.

  • Default config location: src/trex.config.ts
  • Custom config: pass --config <path>
    • bun run ./src/index.ts --config ./samples/trex.config.ts req getTodo

What you put in trex.config.ts

Your config should register:

  1. Environments
import { env, regEnv } from "../src/trex.lib.ts";

regEnv("public", { JSON_BASE_URL: "https://jsonplaceholder.typicode.com" });
env("public"); // selects the active env
  1. HTTP requests (public APIs, etc.) Use addHttpFunc() (recommended for testing):
import { addHttpFunc } from "../src/trex.lib.ts";

addHttpFunc("getTodo", {
  method: "GET",
  url: "{{JSON_BASE_URL}}/todos/1",
});
  1. Pure TS/JS functions (optional)
import { addFunction } from "../src/trex.lib.ts";

export const sum = addFunction("sum", ({ a, b }: { a: number; b: number }) => a + b);

Templates

The engine supports:

  • {{VAR_NAME}} -> replaced from the active environment vars
  • [[requestName.path]] -> replaced from the data saved by a previous request (after req <requestName>)

Samples

This repo includes samples/trex.config.ts, which hits JSONPlaceholder (public test API).

Run it:

bun run ./src/index.ts --config ./samples/trex.config.ts list
bun run ./src/index.ts --config ./samples/trex.config.ts req getTodo
bun run ./src/index.ts --config ./samples/trex.config.ts req getTodosForUser1
bun run ./src/index.ts --config ./samples/trex.config.ts req createPostSample

Tip: try --filter too:

bun run ./src/index.ts --config ./samples/trex.config.ts req getTodo --filter .title