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 🙏

© 2026 – Pkg Stats / Ryan Hefner

esfp

v0.2.0

Published

Better functional programming in JS

Readme

ES Functional Programming

Improve functional programming in JavaScript

This is a Browserify transform with several features (some non-standard) to improve writing JavaScript in a functional style. This repo also serves as a place to discuss moving JavaScript in a more functional direction, and how to impliment that here.

Features

Here is an example of piping, with implicit return, and cloning an object using spread:

function foo (options) {
  options = { bar: 123, ...options }

  foobar(options)
  | bazqux()
  | oofrab()
}

Install

npm install --save esfp

# with yarn
yarn add esfp

Usage

Load as a browserify transform in whatever tool you use. For example, with CLI:

browserify entry.js -g esfp > out.js

Or with browserify

b.transform('esfp')

Or pull-bundle (for a more functional solution :wink:)

bundle('app.js', [ 'esfp' ])

Pipe operator

To use the pipe operator, you should first be familiar with pull-stream, as it will let you do cool things like async and partial pipelines.

Here we just transform foo | bar | ... chains into pull(foo, bar, ...) calls:

values([1, 2, 3])
| map(x => x * 3)
| drain(console.log)

// into:

pull(
  values([1, 2, 3])
  map(x => x * 3),
  drain(console.log)
)

You can also create streams from other streams (known as a "partial"):

const foo =
  infinity()
  | map(x => x * 100)
  | filter(x => x % 2)

// Use it in another pipeline:
foo | drain(console.log)

See babel-plugin-pull for more details

Implicit return value

You don't need to return the last value in a function:

function foo (x) {
  x % 1 !== 0
}

This is especially useful in combination with the pipe operator and partial streams:

function foo ({ modifier }) {
  values([ 1, 2, 3 ])
  | map(x => x * modifier)
}

foo({ modifier: 3 })
| drain(console.log)

See babel-plugin-implicit-return for more details

JSX pragma h

With transform-react-jsx + pragma: 'h' you have more high-level sytnax creating views with functions.

function foo (e, data) {
  <div onclick=${e}>${data}</div>
}

You can use this with librares like hyperapp instead of having to load babelify + the plugin.

Static type checking

This plugin automatically strips Flow types for static type checking.

Note: It does not actually check the types. Use something like ESLint for that aspect.

function foo (bar: number, baz: number): number {
  return bar + baz
}

This could be replaced with a more functional-style type checking:

// foo : number, number
function foo (bar, baz) {
  return bar + baz
}

Let me know your suggestions


Maintained by Jamen Marz (See on Twitter and GitHub for questions & updates)