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

larvitlog

v0.3.4

Published

a socket message server

Downloads

32

Readme

larvitlog

A small json rest api and websocket server with the main purpose of distributing messages to websocket listerners.

Installation

npm i larvitlog;

Usage

As part of another program

In your start script file, run this:

const Logger = require('larvitlog');

const logger = new Logger({
	port: 80,
	fileStoragePath: '/tmp/files',
	intercom, // Instance of larvitamintercom that is used for broadcasting of log messages
	log // Logging object. Will default to a simple console logger if not provided
});

await logger.start();
console.log('Is up and running');

Logging stuff

To send a message that will be broadcast to listening clients post json in the following format to http://address:port/broadcastMessage

{
	"message": "this is the message", // the only mandatory field,
	"emitType": "message", // optional, if only want to broadcast to certain listeners. Will default to "message" if left out
	"metadata": {} // a json object containing what ever. Will be broadcast to clienents.
}

Reading the backlog

It is possible to request allready logged messages from the server. Send a GET request to http://address:port/getMessages and an array of message objects like the example above will be returned.

URL query parameters limit and level can be specified to filter messages, for instance http://address:port/getMessages?limit=100&level=error&level=warn

Road map

Upcomming features

  • Get messages by date
  • Broadcast messages via rabbit mq