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

cinovo-logger-file

v0.4.5

Published

File endpoint for cinovo-logger.

Downloads

19

Readme

                                                   ___
       __                                         /\_ \
  ___ /\_\    ___     ___   __  __    ___         \//\ \     ___      __      __      __   _ __
 /'___\/\ \ /' _ `\  / __`\/\ \/\ \  / __`\  _______\ \ \   / __`\  /'_ `\  /'_ `\  /'__`\/\`'__\
/\ \__/\ \ \/\ \/\ \/\ \L\ \ \ \_/ |/\ \L\ \/\______\\_\ \_/\ \L\ \/\ \L\ \/\ \L\ \/\  __/\ \ \/
\ \____\\ \_\ \_\ \_\ \____/\ \___/ \ \____/\/______//\____\ \____/\ \____ \ \____ \ \____\\ \_\
 \/____/ \/_/\/_/\/_/\/___/  \/__/   \/___/          \/____/\/___/  \/___L\ \/___L\ \/____/ \/_/
                                                                      /\____/ /\____/
                                                                      \_/__/  \_/__/

Build Status NPM version NPM dependencies

cinovo-logger-file

File endpoint for cinovo-logger.

Getting started

At first you must install and require the logger.

npm install cinovo-logger

Next you must require the module

var logger = require("cinovo-logger");

Append cinovo-logger-file endpoint

npm install cinovo-logger-file

In your JavaScript code append the file endpoint.

logger.append(require("cinovo-logger-file")(true, true, true, true, "./log", "log", ".txt", 1, 60, 10));

Log something

logger.debug("all values are ok");
logger.info("myscript", "all values are ok");
logger.error("myscript", "some values are not ok", {a: 10, b: 20});
logger.exception("myscript", "some values are not ok", new Error("error"));
logger.critical("myscript", "all values are not ok", {a: 10, b: 20}, function(err) { ... });

Done

Now you can log to file endpoint.

API

(debug, info, error, critial, dir, fileSuffix, filePrefix, maxFileSize, maxFileAge, maxFiles, callback)

Async creates a file Endpoint.

  • debug: Boolean - true if the endpoint should log debug level
  • info: Boolean - true if the endpoint should log info level
  • error: Boolean - true if the endpoint should log error level
  • critical: Boolean - true if the endpoint should log critical level
  • dir: String - directory in which log files are saved.
  • filePrefix: String -
  • fileSuffix: String -
  • maxFileSize: Number - bytes
  • maxFileAge: Number - seconds
  • maxFiles: Number - Maximum Number of files in dir (oldest are removed first)
  • callback: Function(err, endpoint) - fired if the endpoint is ready to use
    • err: Error (optional)
    • endpoint: Endpoint - use the endpoint like this logger.append(endpoint)

Events

_stop(lastFile)

When the endpoint is stopped.

  • lastFile: String - path and name

error(err)

Something went wrong in the background e.g. roll because of max age reached.

  • err: Error

openFile(file)

File was opened and is ready to be written.

  • file: String - path and name

Example:

var endpoint = require("cinovo-logger-file")(true, true, true, true, "./log", "log", ".txt", 1, 60, 10);
endpoint.on("openFile", function(file) { ... });
logger.append(endpoint);

createFile(file)

File was created and is ready to be written.

  • file: String - path and name

Example:

var endpoint = require("cinovo-logger-file")(true, true, true, true, "./log", "log", ".txt", 1, 60, 10);
endpoint.on("createFile", function(file) { ... });
logger.append(endpoint);

rollFile(oldFile, newFile)

If the file size gets to big or the file gets to old the current file is replaced with a new one. This is called a roll.

  • oldFile: String - file that is too big or too old (path and name)
  • newFile: String - file ready to be written (path and name)

Example:

var endpoint = require("cinovo-logger-file")(true, true, true, true, "./log", "log", ".txt", 1, 60, 10);
endpoint.on("closeFile", function(file) { ... });
logger.append(endpoint);

closeFile(file)

File was closed and is ready to be written.

  • file: String - path and name

Example:

var endpoint = require("cinovo-logger-file")(true, true, true, true, "./log", "log", ".txt", 1, 60, 10);
endpoint.on("closeFile", function(file) { ... });
logger.append(endpoint);

busy()

If the log file can not be written as fast as you send logs. In this situation you are losing log entries!

ysub()

If the log file can continue to be written.