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 🙏

© 2025 – Pkg Stats / Ryan Hefner

fluential

v0.0.0

Published

Make a chained interface for a library

Readme

#fluential

###Make a chained interface for any library

fluential allows you to take an object containing functions, and produce a new object that can be used as a chained/fluent API.

##Usage

var fluential = require('fluential');
var path = require('path');

// Makes a chained version of the library
var fPath = fluential(path);

// Give the chained library an initial value, perform operations, and then take its .value
var myPath = fPath("C:/Users\\j201")
	.normalize()
	.join("npm", "fluential", "test")
	.resolve("../lib.js")
	.value; // C:\Users\j201\npm\fluential\lib.js

// A custom property can be used instead of .value
var fMath = fluential(Math, 'amazingResult');
fMath(5)
	.sqrt()
	.sin()
	.pow(3)
	.amazingResult; // 0.4869774111455

##Rationale

The most composable functions are those that just map arguments to return values. Those are the kinds of APIs that library developers should be offering, because they're simple, consistent, and give us users the most freedom to manipulate the library functions. And, if we want a different API, tools like this let us use it the way we want. So why should all sorts of library developers each make their own new fluent APIs when we can write one that will work anywhere in less than 50 lines?

##Licence

Licensed under the MIT licence. ©2014 j201