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

rf-logger

v4.0.0

Published

A simple logging utility with a save function.

Downloads

61

Readme

rf-logger

A simple logging utility with a save function.

Setup

The first parameter takes a name or a label that will prefix the log. Usually it's best to just use the name of whatever script is running the logger. If you want to save, the logs to a file, use

{ save: true }.

It will default save to:

./logs.log.

Otherwise, you can specify the path in options:

const logger = new Logger({ filename: "myscript.js", save: false, path: "./logs.log" });

It will save with timestamps in CSV format.

Timestamp format: YYMMDD HH:mm:ss.ms

If you want to import it to a spreadsheet, just change the extension .log to .csv.

Custom Log Name

You can add a custom log name by adding it to settings.

const logger = new Logger({ filename: "myscript.js", customLog: "fatality"});

logger.custom("this might be bad")
// (myscript.js) FATALITY this might be bad

Example

const Logger = require("./index.js");
const logger = new Logger({ filename: "myscript.js", save: false, path: "./logs.log", customLog: "fatality" });

logger.log("hello world")
// (myscript.js) hello world 

logger.info("hello info")
// (myscript.js) <INFO> hello info

logger.warn("hello warning")
// (myscript.js) <WARN> hello warning

logger.error("hello error")
// (myscript.js) <ERROR> hello error

logger.debug("hello debug")
// (myscript.js) <DEBUG> hello debug

logger.custom("hello custom")
// (myscript.js) <FATALITY> hello custom

Saved Output

200803 00:16:54.436, "myscript.js", log, "hello world"
200803 00:16:54.436, "myscript.js", info, "hello info"
200803 00:16:54.436, "myscript.js", error, "hello error"
200803 00:16:54.436, "myscript.js", warn, "hello warning"
200803 00:16:54.436, "myscript.js", fatality, "hello custom"