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

rtfm-logparse

v1.0.1

Published

Parse and search logs. Filter by level, time, pattern.

Readme

logparse

Parse and search log files. Filter by level, time, pattern.

Install

npm install -g logparse

Usage

# Parse log file
logparse app.log

# Filter by level
logparse app.log --level error
logparse app.log -l warn,error

# Filter by time range
logparse app.log --after "2024-01-01"
logparse app.log --before "2024-01-02"
logparse app.log --last 1h

# Search pattern
logparse app.log --grep "connection failed"
logparse app.log -g "timeout"

# Output format
logparse app.log --json
logparse app.log --csv

# Count by level
logparse app.log --count

# Help
logparse --help

Output

$ logparse app.log -l error --last 1h

  logparse - rtfm.codes
  ─────────────────────
  File: app.log
  Filter: level=error, last=1h

  2024-01-01 11:23:45 [ERROR] Database connection failed
  2024-01-01 11:45:12 [ERROR] Timeout waiting for response
  2024-01-01 11:58:03 [ERROR] Invalid token received

  Found: 3 entries

$ logparse app.log --count
  debug:  1,234
  info:   5,678
  warn:     456
  error:    123
  fatal:      2
  ─────────────
  total:  7,493

Supported formats

# Auto-detected formats
2024-01-01 12:00:00 ERROR Something failed
[2024-01-01T12:00:00Z] [ERROR] Something failed
ERROR 2024-01-01 12:00:00 Something failed
{"timestamp":"2024-01-01T12:00:00Z","level":"error","message":"failed"}

License

MIT


rtfm.codes - read the fine manual