Functional Programming with Lodash/FP

We have been hearing a lot about functional programming since the past couple of years and even how to use the paradigm in Javascript. For the ones are used to the Lodash library, know that it exports a module to help with functional programming. We’re about to see the main differences.

First of all, I must say that Lodash should not be your first choice when writing functional programming with Javascript. A better choice would be, probably, Ramda. But if your team likes Lodash very much, or your project already uses it, Lodash/FP may be a good option…

It provides a FP guide listing the main differences of the module. As described on the official page:

The lodash/fp module promotes a more functional programming (FP) friendly style by exporting an instance of lodash with its methods wrapped to produce immutable auto-curried iteratee-first data-last methods.

So, let’s late a look at the main differences.


For web pages, you shall load lodash.fp.min.js along with lodash.min.js from the CDN.

**<script** src='' **></script>**

With Node.js you can just require the lodash/fp module.

**const** _ = require('lodash/fp');

Auto Curried Methods

All methods in Lodash/FP are curried by default. That means that a method will only be executed if all it’s arguments are provided. If not, the method will return a new function which accepts the remaining arguments.

For example, the following calls provide the same result.

**const** object = { foo: 1, bar: 2 };

_.pick(['foo'], object);
*//{ foo: 1 }*

*//{ foo: 1 }*

This is very useful when creating functions with predefined arguments and forgoes the need of _.partial.

**const** pickFoo = _.pick(['foo']);

*//{ foo: 1 }*

Fixed Arity

Lodash has a lot of methods with optional arguments. This isn’t true in Lodash/FP. To allow curry, all methods must have a fixed arity.

For example, the _.merge method in Lodash accepts an unlimited number of arguments.

_.merge({ a: 1 }, { b: 2 }, { c: 3 }, { d: 4 });
*//{ a: 1, b: 2, c: 3, d: 4 }*

In Lodash/FP _.merge has a fixed arity of two. This may sound that the method became less useful, but the same behavior can be achieved with subsequent calls or by using a _.reduce.

_.reduce(_.merge, {}, [{ a: 1 }, { b: 2 }, { c: 3 }, { d: 4 }]);
*//{ a: 1, b: 2, c: 3, d: 4 }*

User Defined Functions

Of course, any user defined function can be curried with the _.curry method.

**const** greet = _.curry((greetings, name) => {
    console.log(`${greetings} ${name}`);

**const** sayHelloTo = greet('Hello');

*//Hello Paulo*

Iterate-First Data-Last

All methods that accepts an iterate function as argument now accepts the collection argument for the last.

*//Lodash*, fn);

*//Lodash/FP*, collection);

This is, again, done to allow creating functions with a predefined iterator.

**const** addOne = => n + 1);

addOne([1, 2, 3]);
*//[2, 3, 4]*

This new approach make them awesome to use with Promises.

**const** _ = require('lodash/fp');
**const** request = require('request-promise-native');

*//read posts from REST API and*
*//convert to a user;title CSV*
.then(['userId', 'title'])))
.then(_.concat([['userId', 'title']]))

*// userId;title*
*// 1;sunt aut facere repellat provident occaecati excepturi optio reprehenderit*
*// 1;qui est esse*
*// 1;ea molestias quasi exercitationem repellat qui ipsa sit aut*
*// ...*


The Lodash/FP documentation is not very intuitive. The FP guide is the only reference for it, adding to the main lodash documentation site, which may lead to some confusion, as the methods are slightly different.

When searching the docs, keep in mind that…

  1. The first argument on the docs is the last in Lodash/FP

  2. Any optional argument is omitted

With these two rules in mind you’ll probably be able to use every method without problems.

This post was first published at

We want to work with you! Check out our "What We Do" page.