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

daily-logfile

v1.0.1

Published

Daily Logfile

Downloads

4

Readme

daily-logfile

Quick and simple cluster-aware logging into daily files.

Use Daily Logfile Logger to log events, data and/or errors into locally generated files. Each logfile is date stamped and only contains logs for that date. Log entries are time stamped to milliseconds.

By default, if application runs on cluster, each cluster node logs into separate file. If cluster identifier is set, then logs are written into single file for all cluster nodes, and log entries are stamped with worker id and process id.

Target: ES2022 [NodeJS][ESM+CJS].

Logging functions

Use functions trace, debug, info, warn, and error to write logs conditionally, depending on specified minimum log level. For example, if minimum log level is INFORMATION then trace and debug will not write into a logfile. Use functions fail and log to write logs unconditionally.

LogLevel enumeration

Logger allows logging with the following levels:

  • TRACE
  • DEBUG
  • INFORMATION
  • WARNING
  • ERROR
  • FAILURE

Logger configuration parameters

  • dir: Logfile directory, defaults to current working directory.
  • tag: Logfile tag to identify logging application, defaults to empty string.
  • ext: Logfile extension, defaults to 'log'.
  • utc: If true date-time values are in UTC, defaults to false.
  • stack: If true writes error stack trace if available, defaults to false.
  • stdout: If true additionally writes logs to stdout, defaults to false.
  • level: Minimum log level, errors and failures are always logged, defaults to INFORMATION.
  • cluster: Logfile cluster identifier if logs to be written into a single file for all cluster nodes. By default, each cluster node logs into separate logfile [dir|CWD]/YYYY-MM-DD[.tag].[worker-id].[ext|log], where CWD is current working directory.

If multiple instances of Logger are used, make sure that each instance has different dir/tag/ext combination, and cluster identifier.

How to use Logger

Sample code to log events and errors:

...
const logf = new Logger( { tag: 'test', utc: true } );
...
logf.info( 'log some info' );
logf.log( 'logging some data', { val: 'abc', anotherValue: 'def' }, [ 1, 2 ] );
...
logf.error( 'something went wrong', new Error( 'Test Error' ), obj );
...

Generated logfile

Sample log file 2023-07-12.test.log:

|14:18:57|
|349| log some info
|411| logging some data
{"val":"abc","anotherValue":"def"}
[1,2]
|14:18:58|
|010| something went wrong
Test Error
{"objProp1":"a"}