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

yal

v1.3.4

Published

Yet-Another-Logger that pushes logs to log servers with axon to delegate network overhead

Downloads

31

Readme

Build Status

Yet Another Logger that pushes logs to log servers with axon/tcp to delegate network overhead.

If you're like us and you distribute logs to several remote services, you may be using a tool like Winston to do so, and while this is helpful it's also brittle to use in mission-critical applications.

YAL's solution is to simply distribute messages over TCP (via axon) to one or more log servers, delegating the task of processing or shipping messages off to these services. This is especially problematic when logging services are enabled only in production, and thus may not be tested properly locally or in staging environment. This can and likely will bite you.

Check out the YAL server.

Installation

$ npm install yal

About

  • through axon re-connection and failover is supported
  • when NODE_ENV is "development" the log level defaults to "debug"
  • when NODE_ENV is not "development" the log level defaults to "info"
  • when NODE_ENV is "test" the logger will not write to stdio
  • the log level may be altered via the LOG_LEVEL environment variable
  • standard syslog levels are supported: debug, info, warn, error, critical, alert, emergency
  • you may distribute messages to one or more axon log servers
  • YAL writes to stdio for local logging / debuggin
  • YAL sends a creation .timestamp
  • YAL sends the .hostname

Example

The following example shows two servers, with the logger doing round-robin requests between the two.

var Logger = require('yal');

var log = new Logger([
  'tcp://localhost:5000',
  'tcp://localhost:5001'
]);

setInterval(function(){
  log.info('viewed page', { user: 'tobi' });
}, 300);

setInterval(function(){
  log.info('signed in', { user: 'jane' });
}, 1000);

setInterval(function(){
  log.error('oh no boom', { something: 'here' });
}, 3000);

API

Logger(addresses)

Pass a string or array of addresses.

.LEVEL(type, msg)

Send a log message.

.silent()

Disable stdio.

License

MIT