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

v0.3.0

Published

A functional, streaming logging library.

Downloads

2

Readme

Fun, furious, functional logging - flogging.js

This library is intended to make logging in functional programming a bit easier. It should play nicely with Ramda.

Please note: This library should still be considered experimental and functions may change at any time.

You are encouraged to read the source and use included libraries directly. Consider this like a Mercury-inspired logging collection.

Installing

npm i flogging --save

Usage

flogging = require('flogging')

R = require('ramda')

log = flogging.start_console_text_stream(process.stdout)

Logs the message and returns the value like it wasn't even there (the logger that is, your values are safe).

lower = R.pipe(
	R.flip(R.divide(2)),
	log.info('Halfway there'),
	R.add(7)
)

what_it_is = lower(30)
// Sets `what_it_is` to 22.
// Prints `{"message": "Halfway there", "value": 15}` to the console.

It's good to clean up after yourself.

log.stop()

Object mode output

Use start_console_stream (note missing _text_) to output the logs to a Stream with objectMode: true.

concat_stream = require('concat-stream')

out_stream = concat_stream((array_of_log_objects) => console.log(array_of_log_objects))

log = flogging.start_console_stream(out_stream)

log.info('Super informational', 12)

log.stop()

I hope it is obvious that using concat-stream like this on all your logs is a bad idea.

License

MIT