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

logq

v0.0.2

Published

A small server/webpage/cli for visualising logs

Downloads

4

Readme

logq

A small server/webpage/cli for visualising logs

Usage

Say you have an application that emits JSON logs. You can use logq similarly to jq:

npm install --global logq

my-server | logq

This will start a webserver which you can view at http://localhost:7001, which renders a simple UI that allows searching your logs using LokiJS find queries.

You can duplicate and remove queries to have multiple log filters appear side-by-side. The queries are parsed as JSON5 (basically, JSON without double-quote requirements and allowing trailing commas).

Under the hood, a websocket server is started as well, meaning the frontend loses it's connection if you kill the server. You can just refresh when you start the server again.

Other installation methods

You could also use npx to avoid installing globally:

my-server | npx logq

Or install it as a dev dependency:

npm install --save-dev logq

Then add a script to package.json:

  "scripts": {
    "dev": "my-server | logq"
  }

Or run from a shell:

my-server | ./node_modules/.bin/logq

You can add --tee to tell it to print the log messages it receives to stdout, so you can pipe them to another tool too.

Status

I wrote this for myself, it may or may not work for you. There's not much of an API, but what there is may change without warning (e.g. --tee - that might be a bastardisation of a linux binary that I don't remember all that well, so could get renamed).

Why is it called logq?

Because the npm package name was available, and it's only four letters so it's easy to type fast. Also I guess because you use it a bit like jq?