\n6. Thank you

Thank you for reading sample chapters of this book. You can purchase the complete book at Leanpub.

",{"_290":291,"_43":44,"_47":48,"_45":46,"_65":66,"_292":293,"_355":288},"previewContent","

\n 1. Introduction\n
- \n 1.1 Installation\n
  - \n 1.1.1 Web\n
  - \n 1.1.2 NodeJS\n
  \n
- \n 1.2 Lodash features\n
- \n 1.3 Code sample convention\n
- \n 1.4 About this book\n
\n
\n 2. Common concepts\n
- \n 2.1 Truthy and falsy\n
- \n 2.2 SameValueZero\n
- \n 2.3 Predicates\n
  - \n 2.3.1 matches\n
  - \n 2.3.2 matchesProperty\n
  - \n 2.3.3 property\n
  \n
- \n 2.4 Iteratees\n
  - \n 2.4.1 Iteratee shorthand\n
  \n
- \n 2.5 this binding\n
\n
\n 3. Collections\n
- \n 3.1 Each\n
- \n 3.2 Every and some\n
- \n 3.3 Filter and reject\n
- \n 3.4 Size\n
- \n 3.5 Includes\n
- \n 3.6 Sample\n
- \n 3.7 Shuffle\n
- \n 3.8 Partition\n
- \n 3.9 Count by\n
- \n 3.10 Group by and key by\n
- \n 3.11 invokeMap\n
- \n 3.12 Map and reduce\n
  - \n 3.12.1 Map\n
  - \n 3.12.2 Reduce\n
  \n
- \n 3.13 Search\n
  - \n 3.13.1 find\n
  - \n 3.13.2 findLast\n
  \n
- \n 3.14 Sort\n
- \n 3.15 flatMap\n
\n
\n 4. String Templates\n
- \n 4.1 interpolate\n
- \n 4.2 escape\n
- \n 4.3 evaluate\n
- \n 4.4 imports\n
- \n 4.5 Data object name\n
\n
\n 5. Recipes\n
- \n 5.1 Filter an object’s properties\n
  - \n 5.1.1 Scenario\n
  - \n 5.1.2 Solution\n
  \n
- \n 5.2 Push an array of elements into an array\n
  - \n 5.2.1 Scenario\n
  - \n 5.2.2 Solution\n
  \n
- \n 5.3 Process data for C3.js pie chart\n
  - \n 5.3.1 Scenario\n
  - \n 5.3.2 Solution\n
  \n
- \n 5.4 Create a unique array of objects\n
  - \n 5.4.1 Scenario\n
  - \n 5.4.2 Solution\n
  \n
- \n 5.5 Convert an array to an object\n
  - \n 5.5.1 Scenario\n
  - \n 5.5.2 Solution\n
  \n
\n
\n 6. Thank you\n
\n Notes\n

\n1. Introduction

\n\n

This book is about the popular JavaScript utilities library lodash. Before we discuss lodash, we should understand why we need a JavaScript utilities library. With the prevalence of Web 2.0, Ajax and NodeJS, JavaScript has become a very important programming language in both browser-side and server-side. Besides the bad parts¹ of JavaScript language, JavaScript itself doesn’t have a rich set of high-level API for developers to use, which makes common programming tasks hard to complete.

\n\n

For example, it’s a very common task to iterate an array and process all elements in this array in sequence. In some old browsers, the JavaScript Array object doesn’t have the method forEach(). To iterate an array, for loop is required as in Listing 1.1. process is the function to process elements in the array.

\n\n

Listing 1.1 Traditional approach to iterate an array

for (var i = 0, n = array.length; i < n; i++) {\n  process(array[i]);\n}\n

\n\n\n\n

When using the method forEach(), the code in Listing 1.1 can be simplified as in Listing 1.2.

\n\n

Listing 1.2 Use forEach() to iterate an array

array.forEach(process);\n

\n\n\n\n

Comparing code snippets in Listing 1.1 and Listing 1.2, it’s obvious that Listing 1.2 is much simpler to understand and easier to write and maintain than the code in Listing 1.1. That’s why developers want more high-level APIs. JavaScript itself is evolving to add more language features and APIs, but the process is not fast enough. ECMAScript, the specification behind JavaScript, includes nine new methods for searching and manipulating array contents in 5th edition. This means developers can use the method forEach() when the JavaScript engine supports ECMAScript 5. But some old browsers, like IE 8, don’t support ECMAScript 5, which means developers need to consider cross-platform compatibility issues if supporting old browsers is a must. ECMAScript 6 specification was published in June 2015 with a lot of new features and enhancements.

\n\n\n\n

Developers rely on JavaScript libraries to make daily development easier. The goal of libraries is to become the bridge between JavaScript runtime and developers. Developers can enjoy the high-level APIs provided by those libraries. Libraries are responsible for handling implementation details about how to use the low-level JavaScript APIs efficiently.

\n\n

You may have heard about or even used another JavaScript utilities library Underscore. Underscore provides a rich set of common APIs in the namespace _. Lodash also uses namespace _ and it’s a drop-in replacement of Underscore with more features and performance improvements. If you already use Underscore, you can simply replace the Underscore with lodash, everything should just work.

\n\n

This book is for the latest lodash 4.17.21 version.

\n\n

\n1.1 Installation

\n\n

Lodash is just a plain old JavaScript library, so it’s very easy to install and use.

\n\n

\n1.1.1 Web

\n\n

In a web application, we can just download the lodash release JavaScript file and include it in the HTML page, then use _ in the JavaScript code.

\n\n

Listing 1.3 Install lodash in HTML page

<script src=\"lodash.js\"></script>\n

\n\n\n\n

We can also use links provided by CDN servers to load lodash. CDN servers usually have different versions of lodash to choose from. Listing 1.4 shows how to use cdnjs to load lodash. cdnjs also provides the minified JavaScript version with source mapping file.

\n\n

Listing 1.4 Load lodash from cdnjs

<script src=\"//cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.21/lodash.js\">\n</script>\n

\n\n\n\n\n\n

\n1.1.2 NodeJS

\n\n

In NodeJS, we can install lodash using npm or yarn; see Listing 1.5 and Listing 1.6.

\n\n

Listing 1.5 Install lodash using npm

$ npm install --save lodash\n\n$ npm install --save lodash@4.17.21\n

\n\n\n\n

Listing 1.6 Install lodash using yarn

$ yarn add lodash\n\n$ yarn add lodash@4.17.21\n

\n\n\n\n

Then we can use require to import lodash package, see Listing 1.7.

\n\n

Listing 1.7 Use lodash in NodeJS

var _ = require('lodash'); // Require the whole lodash package\n\nvar forEach = require('lodash/forEach'); // Require only forEach\n

\n\n\n\n

It’s recommended to only install NodeJS modules of actually used modules. For example, if the code only uses _.forEach method, then install the lodash.foreach module only.

\n\n

Listing 1.8 Use lodash modules

$ npm install --save lodash.foreach\n\nvar forEach = require('lodash.foreach');\n

\n\n\n\n

\n1.2 Lodash features

\n\n

Lodash focuses on providing core features that are frequently used for JavaScript built-in objects, including:

\n\n

Arrays
Objects
Functions
Strings

\n\n

Some of those features may have been included in the latest version of ECMAScript specification. Some platforms may have also implemented extra features. If the underlying platform already supports a certain feature, lodash just uses the native implementation to improve performance.

\n\n

\n1.3 Code sample convention

\n\n

All code samples in this book are written in ECMAScript 6 JavaScript syntax and tested on NodeJS 6.9.4. Most of the code is written as Jest test cases to verify the result. For those code that are not written as Jest code, the result of execution is provided below the actual code as a comment; see Listing 1.9.

\n\n

Listing 1.9 Code sample convention

_.min([1, 2, 3]);\n// -> 1\n

\n\n\n\n

As in the Listing 1.9 above, _.min([1, 2, 3]); is the actual code, 1 after // -> is the execution result.

\n\n

The complete source code of this book can be found on GitHub.

\n\n

\n1.4 About this book

\n\n

Lodash is a well-documented JavaScript library with comprehensive official documentation. This book is a simple and concise guide on how to use lodash in practice. It covers core features and most frequently used functions.

\n\n\n

\n2. Common concepts

\n\n

Before diving into details of lodash functions, we start from some common concepts in lodash.

\n\n

\n2.1 Truthy and falsy

\n\n

Truthy and falsy values are very important when using lodash predicates. false, 0, \"\"(empty string), null, undefined and NaN are falsy values in JavaScript. All other values are truthy values.

\n\n

\n2.2 SameValueZero

\n\n

SameValueZero is the algorithm of how to compare two values in lodash. It’s similar to JavaScript “strict equality comparison” (===), except the handling of NaN. It always makes developers confused as NaN === NaN returns false. SameValueZero removes that confusion, so NaN is the same to NaN in SameValueZero algorithm.

\n\n

\n2.3 Predicates

\n\n

Predicate functions only return truthy or falsy values. They are used frequently in lodash. For example, when filtering a collection, a predicate function is required to determine what kind of elements should be kept.

\n\n

Predicate functions can be written as plain old JavaScript functions. Lodash also provides some helper functions to generate predicate functions for common use cases.

\n\n

\n2.3.1 `matches`\n

\n\n

_.matches(source) takes a source object and creates a new function which performs a deep comparison between the given object and the source object. _.matches supports comparison of different types of data, including booleans, numbers, strings, Date objects, RegExp objects, Object objects and arrays. Listing 2.1 shows how _.matches works by comparing strings and objects.

\n\n

Listing 2.1 Match by object comparison

const matches = require('lodash/matches');\n\ndescribe('matches', () => {\n  it('should match strings', () => {\n    let f = matches('hello');\n    expect(f('world')).toBe(false);\n    expect(f('hello')).toBe(true);\n  });\n\n  it('should match objects', () => {\n    let f = matches([{a: 1}, {b: 2}]);\n    expect(f([{a: 1}, {b: 3}])).toBe(false);\n  });\n});\n

\n\n\n\n

\n2.3.2 `matchesProperty`\n

\n\n

_.matchesProperty(path, value) takes a property path and the expected value of this property path to create a new function that checks if the given object’s value of the same property path matches the expected value. Listing 2.2 shows how _.matchesProperty works by matching simple property name, built-in property and nested property path.

\n\n

Listing 2.2 Match by comparing property value

const matchesProperty = require('lodash/matchesProperty');\n\ndescribe('matchesProperty', () => {\n  it('should match property name', () => {\n    let f = matchesProperty('name', 'Alex');\n    expect(f({name: 'Alex'})).toBe(true);\n  });\n\n  it('should match built-in property', () => {\n    let f = matchesProperty('length', 5);\n    expect(f('hello')).toBe(true);\n  });\n\n  it('should match nested path', () => {\n    let f = matchesProperty('user.name', 'Alex');\n    expect(f({user: {name: 'Alex'}})).toBe(true);\n  });\n});\n

\n\n\n\n

\n2.3.3 `property`\n

\n\n

_.property(path) takes a property path and creates a new function which returns the value of this property path in the given object. _.property can be used to create predicate functions with property values converted to truthy or falsy values.

\n\n

Listing 2.3 Extract property value

const property = require('lodash/property');\n\ndescribe('property', () => {\n  it('should extract property value', () => {\n    let f = property('name');\n    expect(f({name: 'Alex'})).toBe('Alex');\n  });\n});\n

\n\n\n\n

For lodash functions which accept predicates, e.g. _.find and _.filter, predicates can be specified using functions, strings, and objects.

\n\n

If a function is provided, it’s used directly. The predicate matches if the function returns a truthy value.
If only a string is provided, it’s used to create a function using _.property as the predicate.
If an array that contains a string and a value is provided, the string and the value are used to create a function using _matchesProperty as the predicate.
If an object is provided, it’s used to create a function using _.matches as the predicate.

\n\n

For example, given an array shown in Listing 2.4,

\n\n

Listing 2.4 Example input JSON array

[\n  {\n    \"name\": \"Alex\",\n    \"age\": 30,\n    \"is_premium\": false\n  },\n  {\n    \"name\": \"Bob\",\n    \"age\": 20,\n    \"is_premium\": true\n  },\n  {\n    \"name\": \"Mary\",\n    \"age\": 25,\n    \"is_premium\": false\n  }\n]\n

\n\n\n\n

_.find returns the first matching element in the array. A JavaScript function can be used as the predicate to _.find. In Listing 2.5, we find the first element with age greater than 18 in the array users. The result is the first element with the name Alex.

\n\n

Listing 2.5 Find using a function

const find = require('lodash/find');\n\ndescribe('find with different predicates', () => {\n  it('should find with a function', () => {\n    let user = find(users, user => user.age > 18);\n    expect(user).toBeDefined();\n    expect(user.name).toBe('Alex');\n  });\n});\n

\n\n\n\n

If a string is passed as the predicate, it’s treated as a property name of objects in the array. In Listing 2.6, we find the first element with truthy value of the property is_premium in the array. The actual used predicate is _.property('is_premium'). The result is the second element with the name Bob.

\n\n

Listing 2.6 Find using a property value

it('should find with a property value', () => {\n  let user = find(users, 'is_premium');\n  expect(user).toBeDefined();\n  expect(user.name).toBe('Bob');\n});\n

\n\n\n\n

If an object is passed as the predicate, it’s treated as a search example. Objects in returned results must have exactly the same values for all the corresponding properties provided in the search example. In Listing 2.7, we find the first element with the value of the property name equals to Alex in the array. The actual used predicate is _.matches({ name: 'Alex' }).

\n\n

Listing 2.7 Find using an object

it('should find with an object', () => {\n  let user = find(users, { name: 'Alex' });\n  expect(user).toBeDefined();\n  expect(user.name).toBe('Alex');\n});\n

\n\n\n\n\n\n

\n2.4 Iteratees

\n\n

Iteratees are used by lodash functions which require iterating through a collection. Iteratee is invoked for each element in the collection and the result is used instead of the original element. Iteratees are typically used to transform collections. A typical usage of iteratee is in the function _.map. The second argument of _.map is the iteratee. The result of applying iteratee to each element in the collection is collected and returned. In Listing 2.8, we use a function to transform input array [1, 2, 3] to [3, 6, 9].

\n\n

Listing 2.8 map using an iteratee function

const map = require('lodash/map');\n\ndescribe('map with iteratees', () => {\n  it('should map with an iteratee function', () => {\n    let result = map([1, 2, 3], n => n * 3);\n    expect(result).toEqual([3, 6, 9]);\n  });\n});\n

\n\n\n\n\n\n

\n2.4.1 Iteratee shorthand

\n\n

When iteratee functions are required, we can also use the similar syntax as predicate functions to quickly create them. These iteratee shorthands use methods _.matches, _.matchesProperty or _.property behind the scene.

\n\n

In the second invocation of _.map in Listing 2.9, the second argument of _.map must be an array to indicate that it uses _.matchesProperty.

\n\n

Listing 2.9 map using an iteratee shorthand

it('should map with iteratee shorthands', () => {\n  let result = map(users, {name: 'Alex'});\n  expect(result).toEqual([true, false, false]);\n\n  result = map(users, ['name', 'Alex']);\n  expect(result).toEqual([true, false, false]);\n\n  result = map(users, 'name');\n  expect(result).toEqual(['Alex', 'Bob', 'Mary']);\n});\n

\n\n\n\n

\n2.5 `this` binding

\n\n

In Lodash 3, we can use the argument thisArg to specify the value of this binding. In Lodash 4, thisArg has been removed in most methods. To specify the binding object, _.bind should be used explicitly. In Listing 2.10, when the function add is invoked, this value is bound to obj.

\n\n

Listing 2.10 map with this binding using _.bind

const map = require('lodash/map');\nconst bind = require('lodash/bind');\n\ndescribe('this binding', () => {\n  it('should bind to this', () => {\n    const obj = {\n      val: 10,\n      add: function(n) {\n        return this.val + n;\n      }\n    };\n    let result = map([1, 2, 3], bind(obj.add, obj));\n    expect(result).toEqual([11, 12, 13]);\n  });\n});\n

\n\n\n\n\n\n\n

\n3. Collections

\n\n

A collection is an object that contains iterable elements. In lodash, collections can be arrays, objects, and strings. Lodash has a rich set of functions to work with collections.

\n\n

In this chapter, we use the following JSON array as the sample data fruits for some code samples.

\n\n

Listing 3.1 Sample data fruits

[\n  {\n    \"name\": \"apple\",\n    \"price\": 0.99,\n    \"onSale\": true\n  },\n  {\n    \"name\": \"orange\",\n    \"price\": 1.99,\n    \"onSale\": false\n  },\n  {\n    \"name\": \"passion fruit\",\n    \"price\": 4.99,\n    \"onSale\": false\n  }\n]\n

\n\n\n\n

\n3.1 Each

\n\n

_.each(collection, [iteratee=_.identity]) and _.eachRight(collection, [iteratee=_.identity]) iterate over elements in the collection and invoke the iteratee function. The difference is that _.eachRight iterates from right to left. _.forEach is an alias of _.each, while _.forEachRight is an alias of _.eachRight.

\n\n

Listing 3.2 Iterate collections

const each = require('lodash/each');\n\ndescribe('each', () => {\n  it('should support basic iteration', () => {\n    let sum = 0;\n    each([1, 2, 3], val => sum += val);\n    expect(sum).toEqual(6);\n  });\n});\n

\n\n\n\n

\n3.2 Every and some

\n\n

_.every(collection, [predicate=_.identity]) checks if all elements in the collection match the given predicate.

\n\n

Listing 3.3 Check if all elements match certain condition

const every = require('lodash/every');\n\ndescribe('every', () => {\n  it('should support arrays with functions', () => {\n    let result = every([1, 2, 3, 4], n => n % 2 === 0);\n    expect(result).toBe(false);\n  });\n\n  it('should support arrays with property value', () => {\n    const fruits = [\n      {\n        name: 'apple',\n        price: 1.99,\n        onSale: true\n      },\n      {\n        name: 'orange',\n        price: 0.99,\n        onSale: true\n      }\n    ];\n    let result = every(fruits, ['onSale', true]);\n    expect(result).toBe(true);\n  });\n\n  it('should support objects', () => {\n    const obj = {\n      a: 1,\n      b: 2,\n      c: 3\n    };\n    let result = every(obj, n => n % 2 === 0);\n    expect(result).toBe(false);\n  });\n\n  it('should support strings', () => {\n    let result = every('aaaa', c => c === 'a');\n    expect(result).toBe(true);\n  });\n});\n

\n\n\n\n

_.some(collection, [predicate=_.identity]) is the opposite of _.every which checks if any element in the collection matches the given predicate. _.some doesn’t need to iterate the entire collection and the iteration exits as soon as a matching element is found.

\n\n

Listing 3.4 Check if any element matches certain condition

const some = require('lodash/some');\n\ndescribe('some', () => {\n  it('should support arrays', () => {\n    let result = some([1, 2, 3, 4], n => n % 2 === 0);\n    expect(result).toBe(true);\n  });\n\n  it('should support strings', () => {\n    let result = some('hello', c => c === 'x');\n    expect(result).toBe(false);\n  });\n});\n

\n\n\n\n

\n3.3 Filter and reject

\n\n

_.filter(collection, [predicate=_.identity]) filters a collection by returning elements matching the given predicate. _.reject(collection, [predicate=_.identity]) is the opposite of _.filter that returns elements not matching the given predicate. When _.filter is used to filter objects, only values of matching properties are returned. If you want to keep the original object structure, use _.pick or _.omit instead. When _.filter is used on strings, matching characters are returned in an array.

\n\n

Listing 3.5 Filter a collection

const filter = require('lodash/filter');\n\ndescribe('filter', () => {\n  it('should support arrays', () => {\n    let result = filter(['a', 'b', 'c'], c => c > 'b');\n    expect(result).toEqual(['c']);\n  });\n\n  it('should support objects', () => {\n    const obj = {\n      a: 1,\n      b: 2,\n      c: 3,\n    };\n    let result = filter(obj, n => n > 1);\n    expect(result).toEqual([2, 3]);\n  });\n\n  it('should support strings', () => {\n    let result = filter('hello', c => c !== 'l');\n    expect(result).toEqual(['h', 'e', 'o']);\n  });\n});\n

\n\n\n\n

Listing 3.6 shows the examples of _.reject.

\n\n

Listing 3.6 Reject elements in a collection

const reject = require('lodash/reject');\n\ndescribe('reject', () => {\n  it('should support arrays', () => {\n    let result = reject(['a', 'b', 'c'], c => c > 'b');\n    expect(result).toEqual(['a', 'b']);\n  });\n});\n

\n\n\n\n\n\n

\n3.4 Size

\n\n

_.size(collection) gets the size of a collection. For arrays, the size is the array’s length, same as the array’s property length. For objects, the size is the number of own enumerable properties, i.e. the length of the array returned by _.keys. For strings, the size is the string’s length.

\n\n

Listing 3.7 Get the size of a collection

const size = require('lodash/size');\n\ndescribe('size', () => {\n  it('should support arrays', () => {\n    expect(size([1, 2])).toEqual(2);\n  });\n\n  it('should support objects', () => {\n    expect(size({\n      a: 1,\n      b: 2,\n      c: 3,\n    })).toEqual(3);\n  });\n\n  it('should support strings', () => {\n    expect(size('hello')).toEqual(5);\n  });\n});\n

\n\n\n\n

\n3.5 Includes

\n\n

_.includes(collection, value, [fromIndex=0]) checks if a collection contains the given value. An optional index can be provided as the starting position to search. If the collection is an object, values of this object’s properties, i.e. the result of _.values, are searched instead. _.includes uses the SameAsZero algorithm to check equality.

\n\n

Listing 3.8 Check if a collection contains the given value

const includes = require('lodash/includes');\n\ndescribe('includes', () => {\n  it('should support arrays', () => {\n    expect(includes(['a', 'b', 'c'], 'a')).toBe(true);\n  });\n\n  it('should support arrays with index', () => {\n    expect(includes(['a', 'b', 'c'], 'a', 1)).toBe(false);\n  });\n\n  it('should support objects', () => {\n    expect(includes({\n      a: 1,\n      b: 2,\n      c: 3\n    }, 1)).toBe(true);\n  });\n\n  it('should support strings', () => {\n    expect(includes('hello', 'h')).toBe(true);\n  });\n});\n

\n\n\n\n

\n3.6 Sample

\n\n

_.sample(collection) gets a single random element from a collection. _.sampleSize(collection, [n=1]) gets n random elements with unique keys from a collection.

\n\n

Listing 3.9 Get random elements from a collection

_.sample(['a', 'b', 'c']);\n// -> 'a'\n\n_.sample({\n  a: 1,\n  b: 2,\n  c: 3\n});\n// -> 1\n\n_.sample('hello');\n// -> 'h'\n\n_.sampleSize('hello', 2)\n// -> ['h', 'l']\n

\n\n\n\n

\n3.7 Shuffle

\n\n

_.shuffle(collection) shuffles a collection by generating a random permutation. Lodash uses the Fisher-Yates shuffle algorithm to shuffle the collection. For objects, the return value of _.shuffle is a random permutation of the property values.

\n\n

Listing 3.10 Shuffle a collection

_.shuffle(['a', 'b', 'c']);\n// -> ['b', 'c', 'a']\n\n_.shuffle({\n  a: 1,\n  b: 2,\n  c: 3\n});\n// -> [1, 2, 3]\n\n_.shuffle('hello');\n// -> ['l', 'l', 'o', 'h', 'e']\n

\n\n\n\n\n\n

\n3.8 Partition

\n\n

_.partition(collection, [predicate=_.identity]) splits a collection into two groups based on the result of invoking the predicate on each element. The first group contains elements for which the predicate returns a truthy value, while the second group contains elements for which the predicate returns a falsy value.

\n\n

Listing 3.11 Split a collection into two groups

const partition = require('lodash/partition');\nconst fruits = require('../data/fruits.json');\n\ndescribe('partition', () => {\n  it('should support arrays', () => {\n    let result = partition(['a', 'b', 'c'], char => char > 'a');\n    expect(result.length).toBe(2);\n    expect(result[0]).toEqual(['b', 'c']);\n    expect(result[1]).toEqual(['a']);\n  });\n\n  it('should support predicate syntax', () => {\n    let result = partition(fruits, 'onSale');\n    expect(result.length).toBe(2);\n    expect(result[0].length).toBe(1);\n    expect(result[1].length).toBe(2);\n  });\n\n  it('should support strings', () => {\n    let result = partition('hello', char => char > 'l');\n    expect(result.length).toBe(2);\n    expect(result[0]).toEqual(['o']);\n    expect(result[1]).toEqual(['h', 'e', 'l', 'l']);\n  });\n});\n

\n\n\n\n

\n3.9 Count by

\n\n

_.countBy(collection, [iteratee=_.identity]) applies a function to each element in the collection and counts the number of occurrences of each result. The counting result is returned as an object with the applied result as the keys and the count as the corresponding values.

\n\n

Listing 3.12 Count the number of occurrences

const countBy = require('lodash/countBy');\n\ndescribe('countBy', () => {\n  it('should support arrays', () => {\n    expect(countBy([1, 2, 3], n => n > 1)).toEqual({\n      true: 2,\n      false: 1,\n    });\n  });\n\n  it('should support objects', () => {\n    expect(countBy({\n      a: 1,\n      b: 1,\n      c: 2,\n    }, val => val / 2)).toEqual({\n      1: 1,\n      0.5: 2,\n    });\n  });\n\n  it('should support strings', () => {\n    expect(countBy('hello', char => char === 'l')).toEqual({\n      true: 2,\n      false: 3,\n    });\n  });\n});\n

\n\n\n\n

\n3.10 Group by and key by

\n\n

_.groupBy(collection, [iteratee=_.identity]) applies a function to each element in the collection and groups the elements by the result. Elements that have the same result will be in the same group. The grouping result is returned as an object. The keys in the object are the applied results, while the values are arrays of elements which generate the corresponding result.

\n\n

Listing 3.13 Group elements

const groupBy = require('lodash/groupBy');\n\ndescribe('groupBy', () => {\n  it('should support arrays', () => {\n    expect(groupBy([1, 2, 3], n => n > 1)).toEqual({\n      true: [2, 3],\n      false: [1],\n    });\n  });\n\n  it('should support objects', () => {\n    expect(groupBy({\n      a: 1,\n      b: 1,\n      c: 2,\n    }, val => val / 2)).toEqual({\n      1: [2],\n      0.5: [1, 1],\n    });\n  });\n\n  it('should support strings', () => {\n    expect(groupBy('hello', char => char === 'l')).toEqual({\n      true: ['l', 'l'],\n      false: ['h', 'e', 'o'],\n    });\n  });\n});\n

\n\n\n\n

The difference between _.countBy and _.groupBy is that _.countBy only returns the number of grouped elements.

\n\n

_.keyBy(collection, [iteratee=_.identity])’s behavior is similar to _.groupBy, but _.keyBy only keeps the last element for each key.

\n\n

Listing 3.14 Get the last element of grouping

const keyBy = require('lodash/keyBy');\n\ndescribe('keyBy', () => {\n  it('should support arrays', () => {\n    expect(keyBy([1, 2, 3], n => n > 1)).toEqual({\n      true: 3,\n      false: 1,\n    });\n  });\n\n  it('should support objects', () => {\n    expect(keyBy({\n      a: 1,\n      b: 1,\n      c: 2,\n    }, val => val / 2)).toEqual({\n      1: 2,\n      0.5: 1,\n    });\n  });\n\n  it('should support strings', () => {\n    expect(keyBy('hello', char => char === 'l')).toEqual({\n      true: 'l',\n      false: 'o',\n    });\n  });\n});\n

\n\n\n\n

\n3.11 `invokeMap`\n

\n\n

_.invokeMap(collection, path, [args]) invokes a method on each element in the collection and returns the results in an array. The method to invoke is specified by the path, can be the function’s name or the function itself. Additional arguments can also be provided for the method invocation. In Listing 3.14, when the function is invoked, this references the current element.

\n\n

Listing 3.15 Invoke a method on each element in the collection

const invokeMap = require('lodash/invokeMap');\n\ndescribe('invokeMap', () => {\n  it('should support method names', () => {\n    expect(invokeMap(['a', 'b', 'c'], 'toUpperCase')).toEqual(['A', 'B', 'C']\\\n);\n  });\n\n  it('should support extra arguments', () => {\n    expect(invokeMap([['a', 'b'], ['c', 'd']], 'join', ''))\n      .toEqual(['ab', 'cd']);\n  });\n\n  it('should support functions', () => {\n    expect(invokeMap([{a: 1}, {a: 2}], function(toAdd) {\n      return this.a + toAdd;\n    }, 3)).toEqual([4, 5]);\n  });\n});\n

\n\n\n\n

\n3.12 Map and reduce

\n\n

Map and reduce are common operations when processing collections. Map transforms a collection into another collection by applying an operation to each element in the collection. Reduce transforms a collection into a single value by accumulating results of applying an operation to each element. The result of the last operation is used as the input of the current operation.

\n\n

\n3.12.1 Map

\n\n

_.map(collection, [iteratee=_.identity]) is the generic map function. We can use the different iteratee syntax.

\n\n

Listing 3.16 Generic map operation

const map = require('lodash/map');\n\ndescribe('map', () => {\n  it('should support arrays', () => {\n    expect(map([1, 2, 3], n => n * 2)).toEqual([2, 4, 6]);\n  });\n\n  it('should support iteratee syntax', () => {\n    const users = [\n      {\n        name: 'Alex',\n      },\n      {\n        name: 'Bob',\n      }\n    ];\n    expect(map(users, 'name')).toEqual(['Alex', 'Bob']);\n    expect(map(users, {name: 'Alex'})).toEqual([true, false]);\n  });\n});\n

\n\n\n\n

\n3.12.2 Reduce

\n\n

_.reduce(collection, [iteratee=_.identity], [accumulator]) has similar arguments list with _.map, except that it accepts an optional value as the initial input of the first reduce operation. If the initial value is not provided, the first element in the collection is used instead. The provided iteratee function will be invoked with four arguments, accumulator, value, index/key and collection. accumulator is the current reduced value, while value is the current element in the collection. The returned result of the iteratee function invocation is passed as the accumulator value of the next invocation.

\n\n

Listing 3.17 Use _.reduce to sum the values in an array

const reduce = require('lodash/reduce');\n\ndescribe('reduce', () => {\n  it('should support no initial value', () => {\n    let result = reduce([1, 2, 3],\n      (accumulator, value) => accumulator + value);\n    expect(result).toEqual(6);\n  });\n\n  it('should support initial value', () => {\n    let result = reduce([1, 2, 3],\n      (accumulator, value) => accumulator + value, 100);\n    expect(result).toEqual(106);\n  });\n});\n

\n\n\n\n

_.reduceRight(collection, [iteratee=_.identity], [accumulator] is similar to_.reduce) except _.reduceRight iterates all the elements from right to left.

\n\n

Listing 3.18 Reduce elements from right to left

const reduceRight = require('lodash/reduceRight');\nconst reduce = require('lodash/reduce');\n\ndescribe('reduceRight', () => {\n  it('should support strings', () => {\n    let result = reduceRight('hello',\n      (accumulator, value) => accumulator.toUpperCase() + value);\n    expect(result).toEqual('OLLEh');\n\n    result = reduce('hello',\n      (accumulator, value) => accumulator.toUpperCase() + value);\n    expect(result).toEqual('HELLo');\n  });\n});\n

\n\n\n\n

\n3.13 Search

\n\n

Search is a very common task in programming. Search is performed on iterable collections with given conditions. The return result is the first element in the collection matching the condition, or undefined if no matching element is found.

\n\n

\n3.13.1 `find`\n

\n\n

_.find(collection, [predicate=_.identity], [fromIndex=0]) is the generic function to search in collections. When invoking _.find, the collection itself and the search condition should be provided. We can also provide an optional starting index for the search. _.find supports the same predicate syntax. If a function is provided as the predicate, the function is invoked for each element in the array until the function returns a truthy value. The function is invoked with three arguments: the currently iterated element, index or key of the element and the collection itself.

\n\n

Listing 3.19 Find

const find = require('lodash/find');\nconst fruits = require('../data/fruits.json');\n\ndescribe('find', () => {\n  it('should support function predicates', () => {\n    let result = find(fruits, fruit => fruit.price <= 2);\n    expect(result).toBeDefined();\n    expect(result.name).toEqual('apple');\n  });\n\n  it('should support property predicates', () => {\n    let result = find(fruits, 'onSale');\n    expect(result).toBeDefined();\n    expect(result.name).toEqual('apple');\n\n    result = find(fruits, ['name', 'orange']);\n    expect(result).toBeDefined();\n    expect(result.name).toEqual('orange');\n  });\n\n  it('should support object predicates', () => {\n    let result = find(fruits, {\n      name: 'passion fruit',\n      onSale: false,\n    });\n    expect(result).toBeDefined();\n    expect(result.name).toEqual('passion fruit');\n  });\n});\n

\n\n\n\n

\n3.13.2 `findLast`\n

\n\n

_.findLast(collection, [predicate=_.identity], [fromIndex=collection.length-1]) is similar to _.find, but _.findLast iterates over all elements of the collection in reverse order. For arrays, it searches from the last element. For strings, it searches from the last character. For objects, it searches from the last element of the array of property names returned by _.keys.

\n\n

Listing 3.20 Find in reverse order

const findLast = require('lodash/findLast');\n\ndescribe('findLast', () => {\n  it('should support strings', () => {\n    expect(findLast('hello', char => char < 'f')).toEqual('e');\n  });\n});\n

\n\n\n\n

\n3.14 Sort

\n\n

_.sortBy(collection, [iteratee=_.identity]) sorts a collection in ascending order with results after applying the iteratee function to each element in the collection. The sort is stable, which means it preserves original order for elements with equality. We can use multiple iteratees as sort conditions. If multiple elements in the collection have the same value for the first property name, those elements are sorted using the second property name, and so on.

\n\n

Listing 3.21 Sort a collection

const sortBy = require('lodash/sortBy');\n\ndescribe('sortBy', () => {\n  it('should support simple sort', () => {\n    expect(sortBy([3, 2, 1])).toEqual([1, 2, 3]);\n  });\n\n  it('should support function predicates', () => {\n    let result = sortBy([-3, 2, 1], val => Math.abs(val));\n    expect(result).toEqual([1, 2, -3]);\n  });\n\n  it('should support multiple conditions', () => {\n    const users = [\n      {\n        name: 'David',\n        age: 28,\n      },\n      {\n        name: 'Alex',\n        age: 30,\n      },\n      {\n        name: 'Bob',\n        age: 28,\n      }\n    ];\n    let result = sortBy(users, 'age', 'name');\n    expect(result[0].name).toEqual('Bob');\n    expect(result[1].name).toEqual('David');\n    expect(result[2].name).toEqual('Alex');\n  });\n});\n

\n\n\n\n

\n3.15 `flatMap`\n

\n\n

_.flatMap(collection, [iteratee=_.identity]) invokes an iteratee function to each element in a collection. The result of each iteratee function invocation is an array. All result arrays are concatenated and flattened into a single array as the final result.

\n\n

_.flatMapDeep(collection, [iteratee=_.identity]) is similar to _.flatMap except that _.flatMapDeep recursively flattens the result array until it’s completely flattened.

\n\n

_.flatMapDepth(collection, [iteratee=_.identity], [depth=1]) is similar to _.flatMapDeep except that it only flattens the result at the given times. The default value of depth is 1, so _.flatMapDepth(array, iteratee) is the same as _.flatMap(array, iteratee).

\n\n

Listing 3.22 Example of _.flatMap and _.flatMapDeep

const flatMap = require('lodash/flatMap');\nconst flatMapDeep = require('lodash/flatMapDeep');\n\ndescribe('flatMap', () => {\n  it('should support basic operation', () => {\n    const map = value => [value + 1, value - 1];\n    let result = flatMap([1, 2], map);\n    expect(result).toEqual([2, 0, 3, 1]);\n  });\n\n  it('should support recursion', () => {\n    const map = value => [[value + 1], [value - 1]];\n    let result = flatMap([1, 2], map);\n    expect(result).toEqual([[2], [0], [3], [1]]);\n\n    result = flatMapDeep([1, 2], map);\n    expect(result).toEqual([2, 0, 3, 1]);\n  });\n});\n

\n\n\n\n\n

\n4. String Templates

\n\n

If you want to generate strings from a template, _.template([string=''], [options={}]) is a simple yet powerful function to do that. It can be used by libraries and applications to avoid long string concatenations. Grunt uses _.template to support templates in configuration files. It can also be used in applications to generate HTML markups, messages, emails and more.

\n\n

Listing 10.1 Basic usage of string templates

let tpl = _.template('Hello, <%= name %>. Current time is <%= new Date() %>.'\\\n);\ntpl({\n  name: 'Alex'\n});\n// -> 'Hello, Alex. Current time is Fri Jun 23 2017 20:07:19 GMT+1200 (NZST).'\n

\n\n\n\n

In Listing 10.1, the input argument of _.template is the template itself. In the template, <%= and %> are the delimiters to wrap variables to be evaluated at runtime. _.template returns a new function. After invoking the returned function with a context object that contains actual values of template variables, it returns the generated string. If no value is assigned to a variable, an empty string will be used.

\n\n

_.template supports three types of delimiters, interpolate, escape and evaluate.

\n\n

\n4.1 interpolate

\n\n

interpolate delimiters allow to interpolate variables. The default regular expression pattern to declare interpolated variables is /<%=([\\s\\S]+?)%>/g. Simple variables and complex expressions are both supported. The regular expression pattern of interpolate delimiters can be customized by the property interpolate of the options object.

\n\n

Listing 10.2 Use interpolate delimiters

let tpl = _.template('Hello, <%= name %>, the total amount is <%= order.amoun\\\nt + 10 %>.');\ntpl({\n  name: 'Alex',\n  order: {\n    amount: 100,\n  }\n});\n// -> 'Hello, Alex, the total amount is 110.'\n

\n\n\n\n

\n4.2 escape

\n\n

It’s common to use _.template to generate HTML markups. escape delimiters allow to interpolate variables and escape the result values. The default regular expression pattern to declare escaped variables is /<%-([\\s\\S]+?)%>/g. The pattern can be customized by the property escape of the options object.

\n\n

Listing 10.3 Use escape delimiters

let tpl = _.template('<div><%- markup %></div>');\ntpl({\n  markup: '<span>Hello</span>'\n});\n// -> '<div>&lt;span&gt;Hello&lt;/span&gt;</div>'\n

\n\n\n\n

\n4.3 evaluate

\n\n

evaluate delimiters allow executions of JavaScript code. This kind of delimiters is useful when adding logic to templates, e.g. adding condition checks or loops to the template. The default regular expression pattern to declare JavaScript code is /<%([\\s\\S]+?)%>/g. The pattern can be customized by the property evaluate of the options object.

\n\n

Listing 10.4 Use evaluate delimiters

let tpl = _.template('<% if (a > 0) { %> Good! <% } else { %> Bad! <% } %>');\ntpl({\n  a: 1\n});\n// -> ' Good! '\ntpl({\n  a: -1\n});\n// -> ' Bad! '\n

\n\n\n\n

\n4.4 imports

\n\n

Besides from the context object passed to the function created by _.template, a default object can also be passed to _.template as an additional source when evaluating variables. The object is specified using the property imports of the options object. The default values in the imported object can be overridden by values in the context object.

\n\n

Listing 10.5 Use extra imports

let tpl = _.template('Hi, <%= user %>, you should pay <%= amount * discount %\\\n>.',\n  {\n    imports: {\n      discount: 0.8,\n  }\n});\ntpl({\n  user: 'Alex',\n  amount: 100\n});\n// -> 'Hi, Alex, you should pay 80.'\ntpl({\n  user: 'Bob',\n  amount: 100,\n  discount: 0.9\n});\n// -> 'Hi, Bob, you should pay 90.'\n

\n\n\n\n

The default imports object contains only the lodash object itself with the key _, so lodash methods can be used directly in the expressions.

\n\n

\n4.5 Data object name

\n\n

By default, when evaluating variables in the template, variables use the same names as in the context object. The property variable of the options object sets a name to the context object, then variable names should be changed accordingly.

\n\n

Listing 10.6 Use different variable object name

var tpl = _.template('Hello, <%= user.name %>.', {\n  variable: 'user',\n});\ntpl({\n  name: 'Alex'\n});\n// -> 'Hello, Alex.'\n

\n\n\n\n

In Listing 10.6, the context object’s name is set to user, so user.name accesses the property name of the context object.

\n\n\n

\n5. Recipes

\n\n

This chapter gives some recipes about how to do common tasks using Lodash.

\n\n

\n5.1 Filter an object’s properties

\n\n

\n5.1.1 Scenario

\n\n

Filter a given object by removing certain properties.

\n\n

\n5.1.2 Solution

\n\n

Although _.filter and _.reject can be applied to objects, they cannot be used for this scenario, because _.filter and _.reject return an array of property values after filtering. _.pick, _.pickBy, _.omit and _.omitBy should be used instead.

\n\n

Listing 11.1 Filter a given object by removing certain properties

let fruits = {\n  apple: {\n    name: 'Apple',\n    price: 2.99\n  },\n  orange: {\n    name: 'Orange',\n    price: 1.99\n  },\n  banana: {\n    name: 'Banana',\n    price: 0.5\n  }\n};\n\n_.pickBy(fruits, fruit => fruit.price > 2);\n// -> { apple: { name: 'Apple', price: 2.99 } }\n\n_.pickBy(fruits, (fruit, key) =>  key != 'apple');\n// -> { orange: { name: 'Orange', price: 1.99 },\n//      banana: { name: 'Banana', price: 0.5 } }\n\n_.pick(fruits, 'apple');\n// -> { apple: { name: 'Apple', price: 2.99 } }\n

\n\n\n\n

When a predicate function is passed to _.pickBy or _.omitBy, it’s invoked with three arguments: property value, property name and the object itself.

\n\n

\n5.2 Push an array of elements into an array

\n\n

\n5.2.1 Scenario

\n\n

Given an array of elements, push those elements into another array.

\n\n

\n5.2.2 Solution

\n\n

If using Array’s push method, the whole array will be pushed as a single element.

\n\n

Listing 11.2 Use Array’s push method

let array = [1, 2, 3];\narray.push([4, 5, 6]);\nconsole.log(array);\n// -> [1, 2, 3, [4, 5, 6]]\n

\n\n\n\n

The first solution is to use _.spread to wrap the push method to accept arrays as arguments.

\n\n

Listing 11.3 Use _.spread to wrap push method

let array = [1, 2, 3];\nlet push = _.bind(_.spread(Array.prototype.push), array);\npush([4, 5, 6]);\nconsole.log(array);\n// -> [1, 2, 3, 4, 5, 6]\n

\n\n\n\n

The second solution is to push the array first, then use _.flatten to flatten the array.

\n\n

Listing 11.4: Use _.flatten to flatten the array

let array = [1, 2, 3];\narray.push([4, 5, 6]);\n_.flatten(array);\n// -> [1, 2, 3, 4, 5, 6]\n

\n\n\n\n

\n5.3 Process data for C3.js pie chart

\n\n

\n5.3.1 Scenario

\n\n

C3.js is a popular chart library based on d3.js. C3.js can create pie chart based on data input. But when there are many items in the data set, the pie chart itself becomes very hard to read.

\n\n

Listing 11.5 is the basic code to create a pie chart with 100 items.

\n\n

Listing 11.5 Basic code of create a pie chart

function generateData(num) {\n    var data = [];\n    for (var i = 0; i < num; i++) {\n        data.push(['data' + i, (i <= 20 ? 1000 : 0) +  Math.random() * 10]);\n    }\n    return data;\n}\n\nlet chart = c3.generate({\n    bindto: '#chart',\n    data: {\n      columns: generateData(100),\n      type: 'pie'\n    }\n});\n

\n\n\n\n

Below is how this chart looks like.

\n\n\n

\"Unreadable — Unreadable pie chart with 100 items

\n\n\n

\n5.3.2 Solution

\n\n

One solution is to process the data set first by limiting the number of items. For example, we can only get top 20 items from the data set and all the rest items are summed into a new item called Others. By doing this, the created chart will be more readable.

\n\n

In Listing 11.6, use _.sortBy to sort the data array first based on the second element of the item array. Items in the data array are all arrays, [1] can be used to access the second element in the item array. After the data array is sorted, use _.take to find the top 20 items in the sorted array, then use _.last to find the last one. This last item is used as the threshold to partition the data array. Then we use partition to divide the data array into two groups. The first group groups[0] contains items we want to keep, the second group groups[1] contains items we want to merge. For the second group, we use _.sum to calculate the sum of all the items to merge. The merged item is pushed to the result data array with name Others and sum.

\n\n

Listing 11.6 Use lodash to process data

function processData(data) {\n  var threshold = _(data).sortBy('[1]').take(20).last();\n  if (threshold) {\n    var groups = _.partition(data, function(item) {\n      return item[1] >= threshold[1];\n    });\n    if (_.size(groups[1]) > 0) {\n      groups[0].push(['Others', _.sum(groups[1], '[1]')]);\n    }\n    return groups[0];\n  }\n  return data;\n}\n

\n\n\n\n

After using Listing 11.6 code to process the data first, the chart is much easier to read, see below.

\n\n\n

\n\n\n

\n5.4 Create a unique array of objects

\n\n

\n5.4.1 Scenario

\n\n

Given an array of objects in Listing 11.7, remove duplicate values from the array.

\n\n

Listing 11.7 An array of objects with duplicate values

[\n  {\n    \"name\": \"Alex\",\n    \"age\": 30\n  },\n  {\n    \"name\": \"Bob\",\n    \"age\": 28\n  },\n  {\n    \"name\": \"Alex\",\n    \"age\": 30\n  }\n]\n

\n\n\n\n

\n5.4.2 Solution

\n\n

_.uniq and uniqBy functions can be used to remove duplicate values from an array, but it only uses SameAsZero algorithm to compare values. To perform the deep comparison for elements in the array of Listing 11.7, we need to convert each element into a single value. For example, if the property name is the unique key for each element, use _.uniqBy(array, 'name'). If there is no unique key, you can convert the element into a JSON string.

\n\n

Listing 11.8 Compare array elements as JSON strings

_.uniqBy(array, element => JSON.stringify(element));\n

\n\n\n\n

JSON serialization may generate different results for objects with the same value due to the undermined property enumeration order. For a more consistent result, we should create our own object serialization format. In Listing 11.9, we concatenate name and age properties as the serialization format to determine uniqueness.

\n\n

Listing 11.9 Compare array elements using custom serialization format

_.uniq(array, element => element.name + element.age);\n

\n\n\n\n

\n5.5 Convert an array to an object

\n\n

\n5.5.1 Scenario

\n\n

Given an array of objects with IDs, convert the array to an object with IDs as the keys and array elements as the values.

\n\n

For example, given an array in Listing 11.10, convert it to an object shown in Listing 11.11.

\n\n

List 11.10 An array of objects with IDs

[\n  {\n    \"id\": \"user001\",\n    \"name\": \"Alex\"\n  },\n  {\n    \"id\": \"user002\",\n    \"name\": \"Bob\"\n  }\n]\n

\n\n\n\n

List 11.11 Conversion result of Listing 11.10

{\n  \"user001\": {\n    \"id\": \"user001\",\n    \"name\": \"Alex\"\n  },\n  \"user002\": {\n    \"id\": \"user002\",\n    \"name\": \"Bob\"\n  }\n}\n

\n\n\n\n

\n5.5.2 Solution

\n\n

One solution is to use _.each to iterate the array and set each property in the result object, see Listing 11.12.

\n\n

List 11.12 Solution to use _.each

let result = {};\n_.each(array, function(obj) {\n  result[obj.id] = obj;\n});\n

\n\n\n\n

A better solution is to use _.reduce, see Listing 11.13.

\n\n

List 11.13 Solution to use _.reduce

_.reduce(array, function(result, obj) {\n  result[obj.id] = obj;\n  return result;\n}, {});\n

\n\n\n\n\n

\n6. Thank you

\n\n

Thank you for reading sample chapters of this book. You can purchase the complete book at Leanpub.

\nNotes

1Find out the good parts of JavaScript in Douglas Crockford’s excellent book JavaScript: The Good Parts ↩

\n\n\n

\n\n

\n\n","tocStructure",[294,295,296,297,298,299,300,301,302,303,304,305,306,307,308,309,310,311,312,313,314,315,316,317,318,319,320,321,322,323,324,325,326,327,328,329,330,331,332,333,334,335,336,337,338,339,340,341,342,343,344,345,346,347,348,349,350,351,352,353,354],{"_75":76,"_43":77,"_70":-5,"_78":79,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":85,"_70":-5,"_78":86,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":92,"_70":-5,"_78":93,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":95,"_70":-5,"_78":96,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":98,"_70":-5,"_78":99,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":101,"_70":-5,"_78":102,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":104,"_70":-5,"_78":105,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":76,"_43":107,"_70":-5,"_78":108,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":111,"_70":-5,"_78":112,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":114,"_70":-5,"_78":115,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":117,"_70":-5,"_78":118,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":120,"_70":-5,"_78":121,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":123,"_70":-5,"_78":124,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":126,"_70":-5,"_78":127,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":129,"_70":-5,"_78":130,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":132,"_70":-5,"_78":133,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":135,"_70":-5,"_78":136,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":76,"_43":138,"_70":-5,"_78":139,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":142,"_70":-5,"_78":143,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":145,"_70":-5,"_78":146,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":148,"_70":-5,"_78":149,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":151,"_70":-5,"_78":152,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":154,"_70":-5,"_78":155,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":157,"_70":-5,"_78":158,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":160,"_70":-5,"_78":161,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":163,"_70":-5,"_78":164,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":166,"_70":-5,"_78":167,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":169,"_70":-5,"_78":170,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":172,"_70":-5,"_78":173,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":175,"_70":-5,"_78":176,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":178,"_70":-5,"_78":179,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":181,"_70":-5,"_78":182,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":184,"_70":-5,"_78":185,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":187,"_70":-5,"_78":188,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":190,"_70":-5,"_78":191,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":193,"_70":-5,"_78":194,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":196,"_70":-5,"_78":197,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":76,"_43":199,"_70":-5,"_78":200,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":203,"_70":-5,"_78":204,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":206,"_70":-5,"_78":207,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":209,"_70":-5,"_78":210,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":212,"_70":-5,"_78":213,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":215,"_70":-5,"_78":216,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":76,"_43":218,"_70":-5,"_78":219,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":222,"_70":-5,"_78":223,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":225,"_70":-5,"_78":226,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":228,"_70":-5,"_78":229,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":231,"_70":-5,"_78":232,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":234,"_70":-5,"_78":235,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":237,"_70":-5,"_78":238,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":240,"_70":-5,"_78":241,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":243,"_70":-5,"_78":244,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":246,"_70":-5,"_78":247,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":249,"_70":-5,"_78":250,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":252,"_70":-5,"_78":253,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":255,"_70":-5,"_78":256,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":84,"_43":258,"_70":-5,"_78":259,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":261,"_70":-5,"_78":262,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":91,"_43":264,"_70":-5,"_78":265,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":76,"_43":267,"_70":-5,"_78":268,"_71":80,"_87":-5,"_88":-5,"_89":-5},{"_75":76,"_43":271,"_70":-5,"_78":272,"_71":80,"_87":-5,"_88":-5,"_89":-5},"publicChapterContent","nextChapter","sections",[],"routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

\n6. Thank you

Table of Contents

\n1. Introduction

\n1.1 Installation

\n1.1.1 Web

\n1.1.2 NodeJS

\n1.2 Lodash features

\n1.3 Code sample convention

\n1.4 About this book

\n2. Common concepts

\n2.1 Truthy and falsy

\n2.2 SameValueZero

\n2.3 Predicates

\n2.3.1 matches\n

\n2.3.2 matchesProperty\n

\n2.3.3 property\n

\n2.4 Iteratees

\n2.4.1 Iteratee shorthand

\n2.5 this binding

\n3. Collections

\n3.1 Each

\n3.2 Every and some

\n3.3 Filter and reject

\n3.4 Size

\n3.5 Includes

\n3.6 Sample

\n3.7 Shuffle

\n3.8 Partition

\n3.9 Count by

\n3.10 Group by and key by

\n3.11 invokeMap\n

\n3.12 Map and reduce

\n3.12.1 Map

\n3.12.2 Reduce

\n3.13 Search

\n3.13.1 find\n

\n3.13.2 findLast\n

\n3.14 Sort

\n3.15 flatMap\n

\n4. String Templates

\n4.1 interpolate

\n4.2 escape

\n4.3 evaluate

\n4.4 imports

\n4.5 Data object name

\n5. Recipes

\n5.1 Filter an object’s properties

\n5.1.1 Scenario

\n5.1.2 Solution

\n5.2 Push an array of elements into an array

\n5.2.1 Scenario

\n5.2.2 Solution

\n5.3 Process data for C3.js pie chart

\n5.3.1 Scenario

\n5.3.2 Solution

\n5.4 Create a unique array of objects

\n5.4.1 Scenario

\n5.4.2 Solution

\n5.5 Convert an array to an object

\n5.5.1 Scenario

\n5.5.2 Solution

\n6. Thank you

\nNotes

\n2.3.1 `matches`\n

\n2.3.2 `matchesProperty`\n

\n2.3.3 `property`\n

\n2.5 `this` binding

\n3.11 `invokeMap`\n

\n3.13.1 `find`\n

\n3.13.2 `findLast`\n

\n3.15 `flatMap`\n