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

@pimred/logger

v0.6.2

Published

Write logs in nodejs.

Downloads

103

Readme

Logger

Write logs in nodejs.

Installation

npm install --save @pimred/logger

File logging

Usage

const logger = require('@pimred/logger')('my-logs')
logger.info('Hello logger')

With options

const logger = require('@pimred/logger')('my-logs', { directory: 'different-location', filename: 'my-logs.log'})
logger.info('Hello logger')

API documentation

The module exports a function that can be invoked immediately.
The directory will be created if it's not existing.

Options

|Name |Required|Description| |------------------|--------|-----------| |name|x|Name of the directory where the logfiles will be stored| |options||Optional options| |options.directory||Location of the log directoriesDefault: _logs| |options.filename||Format of the filenameAvailable placeholders: {{YEAR}}, {{MONTH}}, {{DAY}}Default: log_{{YEAR}}_{{MONTH}}_{{DAY}}.txt |

Default options

It's possible to define default options in the process.env scope.

|Name |Mapped to | |---------------------------------------|-------------------| |process.env.PIMRED_LOGGER_DIRECTORY|options.directory| |process.env.PIMRED_LOGGER_FILENAME |options.filename |

Logging to Elasticsearch

Usage

const logger = require('@pimred/logger/dist/elastic')()
logger.info('This message will be stored in Elasticsearch')
logger.warn({ myKey: 'myValue' }, 'This message will include an additional key')

With options

const logger = require('@pimred/logger/dist/elastic')({ indexName: 'my-index-name' })

Options

|Name |Required|Description| |------------------|--------|-------------------------------------| |indexName |x |Name of the index in elastic | |elasticNode | |Connection string to the elastic node| |elasticVersion | |Major Elasticsearch version, e.g. 7 | |elasticUsername | |Authentication credentials: username | |elasticPassword | |Authentication credentials: password |

Default options

It's possible to define default options in the process.env scope.

|Name |Mapped to | |------------------------------------------------|--------------------------| |process.env.PIMRED_LOGGER_ELASTIC_INDEX_NAME|options.indexName | |process.env.PIMRED_LOGGER_ELASTIC_NODE |options.elasticNode | |process.env.PIMRED_LOGGER_ELASTIC_VERSION |options.elasticVersion | |process.env.PIMRED_LOGGER_ELASTIC_USERNAME |options.elasticUsername | |process.env.PIMRED_LOGGER_ELASTIC_PASSWORD |options.elasticPassword |

Logging to Loki

Usage

const logger = require('@pimred/logger/dist/loki')()
logger.info('This message will be stored in Loki - grafana')
logger.warn({ myKey: 'myValue' }, 'This message will include an additional key')

With options

const logger = require('@pimred/logger/dist/loki')({
  labels: {
    job: 'my-job-name'
  },
  propsToLabels: ['myKey'],
  lokiUrl: 'http://loki-ip-address:port'
})

Options

|Name |Required|Description| |------------------|--------|-------------------------------------| |lokiUrl |x |Loki url used to push logs | |labels | |Object with labels will be passed to loki - grafana | |propsToLabels | |Array of strings which is going to be used to create labels from message |

Default options

It's possible to define default options in the process.env scope.

|Name |Mapped to | |------------------------------------------------|-------------------| |process.env.PIMRED_LOGGER_LOKI_URL |options.lokiUrl | |process.env.PIMRED_LOGGER_LOKI_USERNAME |options.username | |process.env.PIMRED_LOGGER_LOKI_PASSWORD |options.password |