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

logrw

v2.0.3

Published

A colourful and updatable logger that implements the levels defined in RFC-5424.

Downloads

8

Readme

Logrw Build Status

Logrw implements the logging levels defined in RFC-5424. This module sends all messages to stdout. Colours are implement to allow easy identification of messages. It is also possible to re-write the previous message, for example to update severity level.

Screenshot

Installing

npm install logrw --save

Usage

Without Timestamps

var logrw = new (require('logrw'))();

With Timestamps

var logrw = new (require('logrw'))(true);

logrw.emergency(args...)

/**
 * Display an emergency message
 *
 * RFC 5424 Severity Level 0
 * Emergency: system is unusable
 *
 * @param {...*} arguments - The message to display
 */
 

logrw.alert(args...)

/**
 * Display an alert message
 *
 * RFC 5424 Severity Level 1
 * Alert: action must be taken immediately
 *
 * @param {...*} arguments - The message to display
 */

logrw.critical(args...)

/**
 * Display a critical message
 *
 * RFC 5424 Severity Level 2
 * Critical: critical conditions
 *
 * @param {...*} arguments - The message to display
 */
 

logrw.error(args...)

/**
 * Display an error message
 *
 * RFC 5424 Severity Level 3
 * Error: error conditions
 *
 * @param {...*} arguments - The message to display
 */
 

logrw.warning(args...) logrw.warn(args...)

/**
 * Display a warning message
 *
 * RFC 5424 Severity Level 4
 * Warning: warning conditions
 *
 * @param {...*} arguments - The message to display
 */

logrw.notice(args...) logrw.ok(args...)

/**
 * Display a notice message
 *
 * RFC 5424 Severity Level 5
 * Notice: normal but significant condition
 *
 * @param {...*} arguments - The message to display
 */

logrw.informational(args...) logrw.info(args...)

/**
 * Display an informational message
 *
 * RFC 5424 Severity Level 6
 * Informational: informational messages
 *
 * @param {...*} arguments - The message to display
 */

logrw.debug(args...)

/**
 * Display a debug message
 *
 * RFC 5424 Severity Level 7
 * Debug: debug-level messages
 *
 * @param {...*} arguments - The message to display
 */

logrw.update() logrw.rw()

/**
 * Move the cursor to the previous line.
 *
 * Subsequent output will replace the contents.
 *
 * @return {Logrw}
 */

A new message can be chained for example logrw.update().info('Replacement message')

Contributing

Please use jshint to lint your code and follow coding style already in place. Once you are happy with your changes ensure you have rebased to clean up your commit history before making a pull request. Commits should be on a per-feature basis where possible.

Issues?

Please report all issues via github issues providing as much detail and steps to reproduce if possible.

License

The MIT License (MIT)

Copyright (c) 2015 Jamie Thompson

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.