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

@varnxy/logger

v1.1.2

Published

Simple logging utility for node

Downloads

12

Readme

@varnxy/logger

Simple logging utility for Node

npm version Build Status codecov

Introduction

The log is using format like this [TIMESTAMP:MSG_TYPE:APP_NAME] MESSAGE

  • TIMESTAMP

    timestamp format is HH:mm:ss.

  • MSG_TYPE

    Type of log like INFO, WARN, ERROR and DEBUG.

  • APP_NAME

    Application name is mean what application you want to inform with.

  • MESSAGE

    Your log message.

API

  • constructor Constructor is have argument for APP_NAME, but this is optional. The default is base on file call the instance.

  • setDirectory When we set the log directory it will never show on the console.

Logger API

  • info

  • warn

  • error

  • debug

    Debug will show when using DEBUG environment.

Logger API is using sprintf from sprintf-js.

DEBUG Environment

To show all log.debug you must set DEBUG=true, but if you want partially debug your application you can set DEBUG environment to APP_NAME into separated with comma.

For Example:

  • DEBUG=index.js
  • DEBUG=callcenter_inbound,callcenter_outbound
  • DEBUG=app.js,controller/home.js

Usage

  • Using Console
const logger = require('@varnxy/logger')

let log = logger('my_app')
log.info('Some Information')
// Output: [2019:02:12:INFO:my_app] Some Information
log.info('The data is: %s', JSON.stringify({foo: 'bar'}))
// Output: [2019:02:12:INFO:my_app] The data is: {"foo": "bar"}
log.warn('Some Information')
// Output: [2019:02:13:WARN:my_app] Some Information
log.warn('Disk Usage: %d', myDisk)
// Output: [2019:02:13:WARN:my_app] Disk Usage: 1050624
log.error('Some Information')
// Output: [2019:02:14:ERROR:my_app] Some Information
log.error('Error Application: %s', err)
// Output: [2019:02:14:ERROR:my_app] Error: Error message
  • Using Log Directory
const logger = require('@varnxy/logger')
logger.setDirectory('./logs')
let log = logger('my_app')
log.info('Some Information')
// Output:
// [2019:02:12:INFO:my_app] Some Information
log.warn('Some Information')
// Output:
// [2019:02:12:INFO:my_app] Some Information
// [2019:02:13:WARN:my_app] Some Information
log.error('Some Information')
// Output:
// [2019:02:12:INFO:my_app] Some Information
// [2019:02:13:WARN:my_app] Some Information
// [2019:02:14:ERROR:my_app] Some Information