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

flogging.console_inputs

v0.2.0

Published

Console-style inputs for flogging.js.

Downloads

1

Readme

Flogging.js console-style inputs

This allows you to make function calls like the Node.js console with flogging.js.

If you are unsure if you want this library, you should probably be using the main flogging.js package.

Installation

npm i flogging.console_inputs --save

This only installs a function to create the logging inputs.

You will need to have a flogging.js base installed and organise your own output.

Usage

This example assumes you have looked at the stream base example and know how to connect the logger to an output Stream.

flogging = require('flogging.stream_base')

logger = flogging.start()

log = require('flogging.console_inputs')(flogging.make_note, flogging.send(logger))

log.info('Purely informational', 12)
// Returns 12
// Logs {"label": "Purely informational", "type": "info", "value": 12}

log.error('Something bad happened', {err: 60})
// Returns {err: 60}
// Logs {"label": "Something bad happened", "type": "error", "value": {err: 60}}

flogging.stop(logger)

Constructor

The setup function accepts 2 parameters:

  • Starter: such as flogging.make_note.

  • Sender: such as flogging.send(logger).

Starter

This provides the interface to logging calls.

Must accept the sender as the first parameter. Should accept 2 more parameters: label and value.

Must create the log message Object and then call the sender with it.

Must return the value (last parameter) passed in.

For example:

curry = require('ramped.curry')

started = curry((sender, label, value) => {
	sender({label: label, value: value})
	return value
})

Sender

Receives a single parameter: the log message Object.

You can add common fields with a pipe here:

curry = require('ramped.curry')
flogging = require('flogging.stream_base')
pipe = require('ramped.pipe')

started = curry(pipe([
	curry((message) => {
		message['name'] = 'my logger'
		return message
	}),
	flogging.send(logger)
]))

Make sure you always return the message Object!

Functions

  • error

  • info

  • log

  • trace

  • warn

Each function simply adds a type property to messages.

License

MIT