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

logatron

v1.1.2

Published

In-memory logging server with network support and per-client state dictionary

Downloads

2

Readme

Logatron

Logatron is a simple in-memory logging server with the following features:

  • clients connect and identify via TCP
  • per-connection circular buffer for log messages
  • per-connection updateable state (key/value pairs)
  • query interface

Usage

const logatron = require('logatron');
const log = logatron();
log.listen(2212, '0.0.0.0');

API

log = logatron(opts)

Create a new instance. Valid options:

  • bufferSize: size of each client's circular log buffer. Defaults to 128.

log.listen(port, [host])

Start the logging server.

log.getClientNames()

Return an array of the names of all connected clients.

log.getClients()

Return a map of client name => { connectedAt: ..., log: ..., state: ... }

log.getClientLog(name)

Get an array of log entries for client name. Each log entry is an array of [timestamp, logMessage]. Throws an error if no such client exists.

log.getClientState(name)

Get a the state dictionary for client name. Throws an error if no such client exists.

Events

Logatron instances are EventEmitters and emit the following events:

  • 'ready' (clientName): a new client has connected and identified
  • 'log' (clientName, message): client clientName logged message
  • 'set' (clientName, key, value): client clientName set key to value
  • 'close' (clientName): client clientName closed its connection

Protocol

Logatron's wire protocol is UTF-8, one command per line.

The first thing clients must do is identify:

IAM bob\n

If the identify command fails (i.e. a syntax error or a client with the given name is already connected), the server will terminate the connection.

Thereafter you can either LOG a message or SET a key/value pair:

LOG this is my log message\n
SET foo bar\n
SET foo keys can have multiple words too!\n

That's all there is to it.

TODO

  • startup script
  • HTTP interface for status reports
  • websocket streaming

License

ISC