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

log-fn

v2.1.0

Published

Logging library build on top of 'chalk' and 'boxen'

Downloads

92

Readme

Log-fn

Logging library build with 'chalk'

Example use

// yarn add log-fn
const log = require('log-fn')
log('foo')

const x = {bar: {baz: 'foo'}}
log({x}, 'pattern')

Typing

log(...inputCollection: Array<any>, rules: String)

Rules

  • Your last argument act as rule for logging.
  • You can pass more than one rule using separator .
  • For example log(1,'icon.back') or log(1,'spin.tag=foo')
  • You can disable log-fn all along by setting process.env.LOG_FN_FLAG to false

Default behaviour

log(x)

log(1,2,3, ["foo"], null) // Line 1
log(1, {a: 1}, undefined) // Line 2
log('foo', 'bar') // Line 3

Line 1 will log all of the inputs using the first color of predefinet set of colors. Line 2 will log all of the inputs using the second color of predefinet set of colors.

When object is passed as part of inputCollection, it will go to the end of the log.

The reason is that chalk works with strings, and objects don't have toString method. So objects are logged with plain console.log, while all other types use chalk.

Line 3 will log only 'foo' as last argument 'bar' is a String and is used as rules option.

With background

(log(x, 'back'))

// if array with object

log(1,2,3, ["foo"], null, 'back') // Line 4
log(1, {a: 1}, undefined, 'back') // Line 5

The same as default behaviour, but we are setting not only the color of the text, but also its background.

Pattern logging

log({ x }, 'pattern')