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

bunyan-whatevs-stream

v1.0.0

Published

A bunyan stream for doing whatevs

Downloads

1

Readme

bunyan-whatevs-stream

Wrap whatever function you like in such a way that you can use it as a bunyan stream.

Installation

npm install --save bunyan-whatevs-stream

Usage

The interface is straightforward. You give it a function or a Promise that resolves to the function you want it to do. For example, (and this would be a silly way to achieve the goal), but suppose you wanted to use this wrapper to console.log your messages. Try the following:

import bunyan from 'bunyan'
import createStream from 'bunyan-whatevs-stream'

const whatevs = Promise.resolve(console.log)

const logger = bunyan.createLogger({
  level: 'info'
, name: 'bunyan-whatevs-stream-silly-example'
, streams: [ { stream: createStream(whatevs) } ]
})

logger.info('Heya!') // This will end up putting 'Heya!' into stdout

Fun, right?

FAQ

  1. Why would I wrap the function it in a Promise?

Because your whatevs may not be ready to go right when you set up the logger. Perhaps your function calls some system you haven't connected to yet. That's fine. Give it a Promise that resolves to your whatevs.

License

ISC License (ISC) Copyright 2016 Such Software, LLC

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.