Update dependency lodash to v3 #35
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.4.0
->^3.0.0
Release Notes
lodash/lodash (lodash)
v3.10.1
Compare Source
v3.10.0
Compare Source
v3.9.3
Compare Source
v3.9.0
Compare Source
v3.8.0
Compare Source
v3.7.0
Compare Source
v3.6.0
Compare Source
v3.5.0
Compare Source
v3.4.0
Compare Source
v3.3.1
Compare Source
v3.3.0
Compare Source
v3.2.0
Compare Source
v3.1.0
Compare Source
v3.0.1
Compare Source
v3.0.0
Compare Source
lodash v3.0.0
After a little over a year & more than 2,000 commits we’re excited to release lodash v3.0.0. lodash follows semantic versioning so with this major release we’ve taken the opportunity to clean house & make some back-compat breaking changes. We’ll get into that in a bit, but first lets talk about all the cool things this release has to offer.
String methods
By popular demand we surveyed the utility landscape for a cross-section of string APIs to add to lodash. We settled on 17 string methods:
_.camelCase, _.capitalize, _.deburr, _.endsWith, _.escapeRegExp,
_.kebabCase, _.pad, _.padLeft, _.padRight, _.repeat, _.snakeCase,
_.startsWith, _.trim, _.trimLeft, _.trimRight, _.trunc, & _.words
There’s familiar methods from ES5, like
_.trim
, & ES6, like_.endsWith
,_.repeat
, &_.startsWith
, as well as some lesser known methods like_.deburr
&_.kebabCase
.Following casing rules with methods like
_.camelCase
,_.kebabCase
, &_.snakeCase
allows for strings to be transformed from say camel case, to kebab case, to snake case, & back again.ES is our jam
Previous versions of lodash added
_.assign
,_.find
,_.findIndex
, & ES template delimiter support. In this release we’re taking our ES adoption up a notch by aligning_.includes
,_.isFinite
, &_.keys
, supporting typed arrays in_.clone
&_.isEqual
, usingSet
&WeakMap
for performance-gains, allowingMap
&WeakMap
to be used as _.memoize.Cache, & supporting ES modularized builds with lodash-cli.Functional goodies
There’s lots of functional goodies in v3 like
_.ary
,_.curryRight
,_.flow
,_.rearg
, & support for customizable argument placeholders in_.bind
,_.bindKey
,_.curry
,_.curryRight
,_.partial
, &_.partialRight
.Also several methods now work out-of-the-box as iteratees for methods like
_.map
&_.reduce
We’ve heard from some functional programming fans that lodash wasn’t functional enough, often citing our method signatures as an issue. To ease composition & currying they’d prefer methods like
_.filter
bepredicate
first &collection
second instead ofcollection
first &predicate
second.It’d be a shame for those fans to lose out on lodash over something as little as method signatures so with v3 we’ve added
_.ary
&_.rearg
. The_.ary
method sets the argument cap of a function &_.rearg
rearranges the arguments provided to a function.You can also use individual packages like lodash.ary, lodash.curry, & lodash.rearg to convert functions.
Combined with _.runInContext you could easily create a version of lodash with auto-curried iteratee-first methods. In fact, that’s what we’ve done! Introducing lodash-fp.
lodash reduces the cost of method wrapping produced by
_.ary
,_.curry
, &_.rearg
by using aWeakMap
to store function metadata. In this way a function is only wrapped once even though it may have_.ary
,_.curry
, &_.rearg
applied.Modules, modules, modules
In lodash v2 we introduced npm packages per-method as well as bundles of modules for AMD & Node.js. With v3 we’ve improved lodash-cli’s ability to inline dependencies allowing us to easily customize inlining per method, enabling a better balance between deep dependency graphs & code duplication.
In addition all modularized dependencies now use the
^
version range, instead of the~
, so they’ll update as needed without you having to worry about it. Moving forward all per-method packages will be independently updated, instead of in bulk, becauselodash-cli
will soon be able to detect changes in packages & automatically bump patch/minor version numbers.The lodash & lodash-compat npm packages now come with modules baked in too.
Perfect for browserify and webpack!
The method modules are organized by category so they’re easy to find.
lodash is available in a variety of other builds & module formats.
Performance
We’ve improved performance 20-40% overall in v3 by better utilizing the JIT in JavaScript engines, using internal helper functions that avoid optimization disqualifications & increase the likelihood of function inlining.
In v3 we’ve also introduced lazily evaluated chaining for massive performance wins in certain scenarios.
As mentioned above we’re using
Set
&WeakMap
for performance-gains which all modern browsers, Node.js, & io.js can benefit from.Breaking changes
lodash v3 is a major bump & we’ve introduced several back-compat breaking changes. One such change is that while we still test against Underscore/Backbone unit tests we’re no longer supporting an Underscore/Backbone build. Over the last year we’ve seen Underscore align more & more with lodash’s API so the need for a separate Underscore build has diminished. If you still need compatibility around some of the edges we recommend leveraging modules in lodash v3 to supplement your Underscore use.
Be sure to check out the changelog for a full rundown of changes & give lodash-migrate a spin to help migrate older lodash code to the latest release.
New Core Member
In closing I want to welcome Benjamin Tan (bnjmnt4n) as an official core member.
Without the efforts of contributors, like Benjamin, lodash v3 would not have happened.
If you dig lodash v3 don't forget to star the repo or
npm star lodash
!Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.