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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@olian/brow

v3.3.0

Published

CLI tool for redirecting logs from the terminal into the browser.

Downloads

1

Readme

brow

CLI tool for viewing cli logs in the browser.

$ node helloworld.js | brow foobar
Mirroring logs at localhost:10005/?foobar

Navigate to localhost:10005 and select "foobar" from the list and you will start seeing the logs from the node index.js process.

(You dont have to provide your own group name, in the example above it was "foobar". If you dont provide one, the top most directory will be used as the group name. Everything piped under the same groupname will be treated as the same log as far as brow is concerned)

How to

  1. Install brow: npm i -g @olian/brow
  2. Spin up the brow server by running: brow-server, this will create a .brow directory in your home directory, this is where your brow config and database will live.
  3. Use brow by piping anything into it: echo Hello World | brow

Why

I started developing brow because I needed a tool that allowed me to collect logs from my home server in a single easy to reach place.