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

orange-soda

v1.0.3

Published

A NodeJs logger

Downloads

16

Readme

Orange Soda

Installation

npm i orange-soda -s

Basic Usage

Leveled Logging

// import the library
const {logger} = require('../dist/index');

// this are leveled log functions
// first the level needs to be set

logger.level = 'debug';

// this means that only levels higher than or equal to debug will be logged
// these for example will be logged...
logger.warn('This is a %s message', 'warn');
logger.debug('This is a %s message', 'debug');

// but this will not...
logger.verbose('This is a %s message', 'verbose');

// the format in which the log messages is output can also be changed like so...
logger.format = 'detailed';

// this will make the leveled logs look diffrent
logger.debug('This is a %s message', 'debug');

Access Logging

// import the library
const {logger} = require('../dist/index');

// import a http router library like express or connect
const express = require('express');
let app = express();

// setup the access logger...
logger.access.format = 'common';

// set the router to use the logging middleware...
app.use(logger.access.middleware());

// handle your requests...
app.use('/', (req, res) => {
  res.send('<h1>Hello World</h1>');
});

// listen for requests...
app.listen(3000);

Logging Groups

Logging groups are collections of logging methods that all have a similar function. The two default logging groups are the leveled group and access group. The leveled group handles any logs that can be leveled. The access group handles logs that pertain to the access of something. For example, the access of a server. Read more on log groups here.

Transports

Transports are like write streams, but they also know how to format log data according to the transport's settings. The default transports are the console and file transports. The console transport writes to standard out and standard error. The file transport writes to the specified file. Read more on transports here

Docs

More detailed documentation can be found here.

License

MIT License