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

@niyojs/logger

v0.0.2

Published

Custom console API with extended functionality.

Downloads

4

Readme

README

A custom console API which provides conditional logging and the capability of storing logs in various environments.

import { Logger, LogStorage } from '@niyojs/logger'

const logger = Logger.create({
  // Origin
  src: 'my-module',
  // Print log messages to the console
  // if the log level of the message is "debug" and below
  level: 'debug',
  storages: [
    new LogStorage({
      // Store log messages if the log level of the message is "warn" and below
      level: 'warn',
      fn: entry => {
        // Your custom function to store log
        // Runs synchronously
      }
    })
  ]
})

// or
const logger = Logger.create({ src: 'example', level: 'info' }).add(
  yourStoragePlugin({
    // ...parameters
  })
)

Below methods can be used for logging in addition to the standard console methods (debug, error, info, warn, trace):

  • fatal: Critical errors (console.error)
  • todo: Todo messages (console.warn)
  • success: Success messages (console.info)
  • newline: Prints new lines to the console

Levels

Default log levels:

| Level | Severity | Description | | ------- | -------- | ---------------- | | off | 0 | Silent mode | | fatal | 1 | Critical errors | | error | 2 | Errors | | success | 3 | Success messages | | info | 4 | Info messages | | todo | 5 | To-do messages | | warn | 6 | Warnings | | debug | 7 | Debugging | | trace | 8 | Tracing |

Log levels can be customized via:

import { setLogLevels } from '@niyojs/logger'
setLogLevels({
  // Your custom log levels
})

Styles

The messages are printed to the console with styles. See DEFAULT_NODE_STYLES (chalk) and DEFAULT_BROWSER_STYLES (css) for their default values.

Log styles can be customized via:

import { setNodeStyles, setBrowserStyles } from '@niyojs/logger'
setNodeStyles({
  // Your custom log levels
})
setBrowserStyles({
  // Your custom log levels
})

Storages

See this example to see how log messages are saved to the files.

You may run all the examples via yarn --cwd packages/logger eg command.