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

@zorzal2/logger

v0.1.4

Published

Preconfigured logger

Downloads

2

Readme

node-logger

Preconfigured logger

Cómo funciona

Instalar

npm install @zorzal2/logger --save

Usar

import logger from '@zorzal2/logger';

// logger es el logger raíz
logger.debug('Hello world!'); // 2019-04-11T18:42:50.636-03:00 [][] DEBUG: Hello world!
logger.info('Max height:', 5 * 4, 'mm') // ... INFO: Max height 20 mm
logger.warning('Received', { status: 404 }) // ... WARNING: Received { "status": 404 }
logger.error(new TypeError('WTF!')) // ... ERROR: TypeError: WTF! at ...(stack completo)...

Logger etiquetado

Esta es la forma aceptada de usarlo. En lugar de usar la instancia principal, crear en cada módulo una subinstancia con una etiqueta que identifique quién está logueando.

//Sublogger con un label:
let mylogger = logger.create('my-module')

mylogger.info('Hello') // 2019-04-11T18:42:50.636-03:00 [my-module][] INFO: Hello

Nivel de logs

El log raíz toma el nivel de la variable de entorno LOG_LEVEL, y si no existe se usa por default all (loguea todos los mensajes). Los valores válidos son: all, debug, info, warning, error, none El valor all equivale a debug a fines prácticos.

Se puede cambiar el nivel en runtime:

logger.setLevel('warning'); // valores válidos: all, debug, info, warning, error, none

Esto afecta a todos los subloggers que se hayan creado, a menos que se les haya especificado un nivel propio.

// Crea un logger con su propio nivel de error
let mylogger = logger.create('my-module', 'error')
// O se le puede asignar un nivel en cualquier momento
mylogger.setLevel('warning');

Contexto

Si existe en el contexto la propiedad TxID, se coloca en las líneas de log automáticamente.