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

@trel-to/cli

v0.3.0

Published

Trel CLI — query logs, traces, and exceptions, and upload web source maps

Readme

@trel-to/cli

CLI for Trel. Query logs, traces, exceptions, and endpoint performance with an MCP key, and upload source maps so production stacks symbolicate.

trel mcp bridges stdio clients to the hosted MCP server. Those tools cover every environment and every app in the project unless you pass environment or service.

Setup

Create an MCP key in Settings → AI Agents & MCP in your Trel dashboard. Ingest keys (trel_sk_…) also work and are the right key for CI source-map uploads.

Usage

npm install -g @trel-to/cli
# or
npx @trel-to/cli <command> [options]

Commands

| Command | Description | |---------|-------------| | logs | Fetch logs with optional filters | | exceptions | List exception groups | | exception <id> | Get exception group details; --resolve / --ack / --ignore / --assign <userId> update it | | releases | Release health: new / regressed / resolved groups, events, source maps (--all for every env) | | sourcemaps inject <dir> | Stamp each JS bundle with a debug id and write it onto the matching .map | | sourcemaps upload <dir> --release <sha> | Upload every *.map under <dir>. Add --inject to stamp debug ids first | | symbols upload <path> | Upload a ProGuard map or dSYM for a release | | logs --tail | Follow new logs (polls every 3s) | | trace <traceId> | Get full trace (spans, logs, exceptions) | | performance | List performance endpoints | | overview | Analytics overview |

Web source maps

release must match the value passed to @trel-to/browser (or React, Vue, Next.js).

export TREL_KEY=trel_sk_…
trel sourcemaps upload ./dist --release "$GIT_SHA" --inject

The Vite and webpack plugins stamp debug ids at build time. sourcemaps inject does the same thing after the build, for pipelines that do not use those plugins.

Options

  • -k, --key <key> — API key (or set TREL_KEY / TREL_MCP_KEY env)
  • -e, --environment <env> — production, staging, development (default: production)
  • --from <ts> — Start: Unix seconds or 1h, 6h, 24h, 7d
  • --to <ts> — End time (Unix seconds)

Examples

export TREL_KEY=trel_mcp_xxx
trel logs --search error
trel logs --from 1h --severity error
trel exceptions --limit 20
trel trace abc123def456
trel releases

Output

  • Default: JSON (easy for AI agents to parse)
  • Logs: use -o text for human-readable one-line format
  • Source map upload: a table of file, debug id, size, and status