Devs have shared their likes and dislikes of both projects in an effort to flesh out a path forward. based on browserifing a file with module.exports = require('lodash|underscore'); Thanks for creating the most used modules! Docs | Just kidding, I already saw how @jdalton "collaborated" with you above: RE @jdalton: @CrossEye to help the discussion and make it easier to digest can you try to keep your points on track and tangents to a minimum. Clearly, you believe your project is so much better right? And please do explain what you mean by "...and haven't had to use Underscore." In your mind, it’s just taking out the "competition", I understand. You signed in with another tab or window. Remove semicolons from `sampleSize` and `baseClone`, Use native filter instead of custom one where possible (. Bumps @types/lodash from 4.14.165 to 4.14.166. 📢. Or where would we be if Oracle could petition a court of law to sue each and every one of us for every API we've ever written or will write? The lodash assign method or the native Object.assign method just copy references to any nested objects that might exist in the given source objects. One position I'm not changing is I don't believe a word you say. I created a gist to get a better apples to apples size compassion https://gist.github.com/xbudex/a03aaf17ab8f984c18f0. Adjust spacing in template string expressions. As a matter of principle, an open source project must be allowed to thrive or perish on its merit. Repository owner Actually you can import a single function using the 'lodash.merge' library import merge from 'lodash.merge' const result: any = merge(obj1, obj2) locked and limited conversation to collaborators, Repository owner And all the meaningful exchange of ideas he had with you later in the thread. For projects that support PackageReference , copy this XML node into the project file to reference the package. Libs are hard work. Doesn't this mean keeping two repositories in sync, each having their own name in package.json? It joined the Dojo Foundation in 2013, and via the jQuery Foundation and JS Foundation, is now part of the OpenJS Foundation.. Summary. In addition, request is on track to replace Underscore as the 3rd most directly depended on npm package by September of this year. Use Git or checkout with SVN using the web URL. We decided to ignore our failing audit for now and wait to see if the new version gets published soon. Let's try not to derail this issue please. Totally fine with me. Search . They can keep it. Lodash-PHP tries to mimick lodash.js as close as possible. This is due to an incomplete fix to CVE-2018-3721. lodash is a modern JavaScript utility library delivering modularity, performance, & extras.. No one is suggesting we "snuff" out competition, we're suggesting a merger to reduce duplication in both of the codebases. And as such, Underscore needs no recognition by either me, you or any other developer to the validity of its merit. Now you believe Underscore should die because people use your project too? Alright, I've quickly fleshed out a draft of what I think a consensus API might look like in the Underdash repo: The idea being — require('underdash') gives you all of the core modules — the super-minimal 90% functions that are all you need a lot of the time. So _.assign, as well as other methods like _.merge, and _.extend are some of the many useful methods for working with objects in a project where lodash is part of the stack. They both do more or less the same thing but with just some note worthy differences. One of them inspired by the other. Changed lodash.groupby and lodash.merge to type="module" Errors: [same as #2] 4.) paket add lodash --version 4.17.11 Because npm doesn't allow name redirects (AFAIK), the merged project would be available as a module under both names for the foreseeable future. To try to get a more apples to apples compairison, this is what I did. use of .tap instead of temporary variables, Downloaded underscore 1.8.3 and lodash-compat 3.9.0, unminified development builds of both, If you stick with Underscore, consider moving to an organization like. Lodash isn't developed in a vacuum. About the name: IMHO the “_ variable reasons” don’t really apply since “lodash” is a play of words on “underscore”. The order and references of result values are determined by the first array. I. So this will not be a getting started post on lodash, or javaScript in general. Successfully merging a pull request may close this issue. Creating copies of those on the other hand, would. This is a big opportunity to simplify/reconsider function naming, and get everything named really nicely. You wouldn't see Ember developers hijacking a Backbone thread to instigate a coup d'état. It's all a "misunderstanding" - I get it. You can also use the npm-stats package to view direct dependents, currently 11,080 for Lodash vs. 9,391 for Underscore. Lodash-PHP. I'm sorry you feel that way. Ideally I'd like the Underscore docs to be written, Strict(er) SemVer. Freudian slip or nah? I don't think I've said that. Because lodash is modular it makes getting a total a bit more involved but you can view the cumulative download stats here, currently 2+ million downloads a day for Lodash & its modules vs. ~300k for Underscore. Missing iteratee call in `groupBy` and `keyBy`. It's clear your only intent by these statements is to demean Underscore itself while offering zero compelling evidence to support your baseless claim. I think @alexindigo means to basically change the npm module "underscore" to be a special build of "lodash"? _.chunk(array, [size=1]) source npm package. And please do explain what you mean by "...and haven't had to use Underscore." @tiandavis just fyi i saw @jridgewell and @jdalton out at brunch last week...I think he's a part of the conspiracy, too!!! Ditching the Lodash name or cutting functionality won't fly for a lot of our users. So why are you pulling this PR stunt here? Site | require('underdash/more') gives you everything. Given the 117,952 (at time of writing) packages that depend upon lodash and for the sanity of those of us that work for organisations that must adhere to rigorous security compliance, could we perhaps agree to merge one of the valid PRs, or at the very least object to them so they may be improved. That collaboration wouldn't work well if we were hostile towards each other. The Lodash library exported as a UMD module. Prototype Pollution is a vulnerability affecting JavaScript. So there is really not much more to say about it beyond additional ways of doing so with and without lodash. I tried to replace underscore with lodash 3.x and a function like _.extend differ. Affected versions of this package are vulnerable to Prototype Pollution. Attacking @jdalton accomplishes nothing... cough cough Ad hominem. Module Formats. A modern JavaScript utility library delivering modularity, performance, & extras. You claim developers “haven’t had to use Underscore”, but yet you offer no statistics to back your claim. The lodash fill method is another method to be aware of when using lodash as it does more or less the same thing as lodash repeat only with arrays rather than strings. That right there helps immensely with many normal use cases. Merge docs as well. If nothing happens, download Xcode and try again. It should have remained locked. There is using the main lodash function as a way to wrap a new array that has a given element length, then using the fill method off of that to fill the array with zeros. That line was crossed and it is not ok. @tiandavis: Stop. The whole point of this thread is discussing a merging of the two projects or at least sharing a common core to reduce duplicated efforts & fragmentation across projects. Where would we be if IBM, in all its former glory, abused its influence to make sure each and every one of us programmed COBOL for a living? Or where would we be if the remanence of Netscape had said to a younger Ryan Dahl, "No no Ryan, server side JavaScript is ours!!" - lodash/lodash We already know your position. For anyone stumbling upon this thread, here's a more complete solution. In many cases this might not preset a problem, but it can result in unexpected behavior now and then it you do not understand the differences between these various methods that ar… Lodash makes JavaScript easier by taking the hassle out of working with arrays, Too much negativity in my inbox. Overview. Hey all. If, in your experience, so many developers prefer Lodash, then why are you even trying to merge the two projects? // Load the FP build for immutable auto-curried iteratee-first data-last methods. These properties will be present on all objects. It will compare two objects and give you the key of all properties that are either only in object1, only in object2, or are both in object1 and object2 but have different values: /* * Compare two objects by reducing an array of keys in obj1, having the * keys in obj2 as the intial value of the result. Lodash is a JavaScript library that helps programmers write more concise and maintainable JavaScript. This is a post on the lodash method _.join, as well as the corresponding Array.prototype.join method that is being referenced. 1: const c = _.assign({}, a, b); If you’d like to learn more about lodash, check out my free e-book about Functional Programming in JavaScript. This is a big opportunity to simplify/reconsider function naming, and get everything named really nicely. Example The one thing which has remained a constant is the motivation from you and a small group of Lodash users is disingenuous at best and malicious at worst. Allow compareMultiple to accept compare functions in addition to orde…. But your comments just sound like sour grapes from someone not able to derail the operation. I want to merge the objects based on a specific key (here label[1]). So let me get this straight...You thought you could make a better Underscore. That entire statement is anecdotal evidence based on your own biased envy of Underscore. JDD got in touch with me over email this morning, inquiring about the possibility of merging Underscore and Lodash together. Consistent use (always) of parentheses in arrow functions. Investigate swapping Underscore w/ Lo-Dash or upgrading Underscore, https://www.npmjs.com/package/lodash.foreach, https://gist.github.com/xbudex/a03aaf17ab8f984c18f0, https://github.com/documentcloud/underscore-contrib, The Name: "Lodash" is very cute, but keeping "Underscore" makes the most sense, both for historical and, Documentation style. So, there would be no friction at all by just continuing to refer to the existing lodash modules. We get it, but it makes tickets hard to have conversations on. numbers, objects, strings, etc. Learn more about github-labels@0.5.2 vulnerabilities. Locking this issue as it's no longer constructive. mjubair changed the title Fix typo in _.reduce documentation Fix typo in _.reduce documentation Fixes #4861 Jul 16, 2020 This blatant, clearly orchestrated, campaign to bring about its demise is an affront to the very nature of open source software - an ecosystem that every single one of us here derive our livelihood. Because it's a fork there is --a lot-- of cross lib collaboration and planning to ensure developers can use either without headache. How does Underscore-Contrib fit in to all this? I was wondering if someone know who I should contact to determine what is permissible as far as naming and licensing, as this is derived from the Lodash … Would be great if github … I wasn't suggesting Underscore change its name either. unlocked this conversation, The Big Kahuna: Underscore + Lodash Merge Thread. Adjust styling of array checks in `head`, `uniq`, `uniqBy` and `uniqW…, Coerce indexOf fromIndex parameter to integer (, Replace getTag implementation by the one from baseGetTag (remove work…, internal: use util.types to migrate DEP0103 in Node.js (. If for some reason you cannot use ES6 language features in your application, you can resort to using the lodash library. Are you implying Underscore is something painful or undesirable to use? Well there you have it, the lodash last method is to just get the last element in the array. I may have missed and or fudged things ... feel free to edit as you like. In addition to this I assume that you have at least a little background with javaScript, and how to get started with lodash or any javaScript asset before hand. Details. Let's kick stuff around a bit. You don't need a new library to do this; just rename everything and then release it as underscore 1.8.4. Or is this just a cheap shot at Underscore? Looking for Lodash modules written in ES6 or smaller bundle sizes? We should take advantage. Before your comments this issue had been closed and done with for ~half a month. No one has malicious intent here, so let's not devolve into bait trolling. Could underscore (on npm) just become an official build of lodash (like lodash-underscore build used to be)? @schmod Getting waaay ahead of the cart here. And as for the naming, how about keeping underscore for the lightweight version of lodash, like basic / core module, but the whole ecosystem will be lodash thing. But this whole "open discussion" is just a red herring and a ruse for your ultimate endgame to consume Underscore and its legacy. As an exercise to the repo collaborators, let's see what it would look like to pull in all of the good stuff from https://github.com/documentcloud/underscore-contrib as well — the more useful of them going in "More" and the more esoteric going in a new third-level "Contrib" section. Fixin scope range for var declarations in `hasPath` and `hasPathIn`. Now you understand there is a line between thinking about taking out the "competition" and actually acting on taking out the "competition". Can't...? History. Point to a single instance where support for Underscore was raised and you had a civil exchange of ideas without outright dismissing the other developer. Affected versions of this package are vulnerable to Prototype Pollution in zipObjectDeep due to an incomplete fix for CVE-2020-8203.. Let's move discussion over to underdash then. Can't...? Not at all. …Too soon? Then there's each package's trending growth. It is a set of easy to use utility functions for everyday PHP projects. You could try to publish it to npm under your own scope and edit the resolution accordingly. Or is this just a cheap shot at Underscore? - a JavaScript repository on GitHub Lodash is the dominate library...by a large margin? Contribute with something substantive instead." This is a joint discussion between Underscore and Lodash communities and core. https://www.npmjs.com/package/lodash.foreach. Review the build differences & pick one that’s right for you. Lodash is the dominate library in node/io.js ecosystems by a large margin and is making its way into projects like Ampersand, Ember, & React*. If there are things Underscore does that Lodash doesn’t, then just copy the functionality like you always have and move on. Creates an array of elements split into groups the length of size.If array can't be split evenly, the final chunk will be the remaining elements. lodash is a modern JavaScript utility library delivering modularity, performance, & extras. Or the other way around? GitHub Gist: instantly share code, notes, and snippets. Sure thing. If all status checks pass Dependabot will automatically merge this pull request. Wiki | I don't think anyone is being dismissive. I suspect that lodash needs to be packaged in some way for any lodash/* import to be available. At almost 65 million downloads over the last two years (keep in mind, the project has been out for longer than that), Underscore has achieved more merit than most of us could ever hope to achieve for a project. A merged project should be available under both names, for least friction. Learn more. Do you actually have any numbers to back this up? From here you can see that in the last month and a half Underscore gained a bit over 360 dependents while Lodash gained well over 1,000 dependents (more than 3x of Underscore). This is a very common problem for github issues posted on HN/any social media. Lodash’s modular methods are great for: Lodash is available in a variety of builds & module formats. Check out lodash-es. You need a GitHub account to be able to sign the CLA. FP Guide | You can also trigger a rebase manually by commenting @dependabot rebase. We help and push each other. For the record, I've followed both threads from the beginning. Your comments are not helpful. I'm prepping lodash v4 which tackles many of the goals/items of the merge to proof things out and I'd dig some feedback over on the Underdash issue. Lodash draws most of its ideas from Underscore.js and now receives maintenance from the original contributors to Underscore.js.. Im looking to merge/combine objects in an array each with a series of nested arrays. You can judge each by their monolithic build numbers then. I'm still of the opinion that true believer SemVer isn't something that actually exists in the real world (most changes are subtly backwards-incompatible in minor ways), but I have no problem praying to this golden cow to keep the philistines happy ;), "Governance Model": I don't think we need anything fancy here. Instead of “polluting” the npm registry with copies of that under a new name like underscore.foreach (i.e. Lodash’s modular methods are great for: Iterating arrays, objects, & strings; Manipulating & testing values; Creating composite functions. Please STOP +1 and :+1: -ing GitHub tickets. If nothing happens, download the GitHub extension for Visual Studio and try again. Importing lodash functions from lodash-es. array (Array): The array to process. lodash typescript lodash online lodash cdn lodash documentation vue-lodash lodash github lodash vs underscore lodash/fp. So let me get this straight...You thought you could make a better Underscore. Direct dependents are one thing but there's also indirect dependents, packages who have Lodash or Underscore somewhere in their dep graph. I encourage you to take some time to reread this thread and its related thread. Added require.js, with lodash.groupby and lodash.merge Errors:-- require.js:5 - Uncaught Error: Module name "lodash.merge" has not been loaded yet for context: _. I've already expressed my doubts about how worthwhile this whole thing is, and I stand by them, even if, as I said, I can't get myself to care too much. [size=1] (number): The length of each chunk Returns (Array): Returns the new array of chunks. It's actually /way/ more dominant than that. Have to agree on the comment "lazy by default" of Lodash. Work fast with our official CLI. The fact that we're discussing, collaborating, and working together is a positive thing. The merge lodash object methods will recursively merge down own and inherited object properties while the lodash assign will just assign properties. // Cherry-pick methods for smaller browserify/rollup/webpack bundles. There's already a decent-sized group of folks who contribute to both Underscore and Lodash with the commit bit. You wanted an exchange of ideas, well here's one... As a community, we should encourage competition, not abuse our influence to snuff it out. If, in your experience, so many developers prefer Lodash, then why are you even trying to merge the two projects? Ensure escapeRegExp returns an empty string when passing falsy values (, Update `filterObject` docs to reference `pickBy` (, Coerce findLastIndex and lastIndexOf fromIndex parameter to integer (. Solution 2: lodash. You claim Lodash is the “dominate library in node/io.js”. Keep in mind, lodash does does have more functionallity along with the larger size. The functions merge, mergeWith, and defaultsDeep could be tricked into adding or modifying properties of Object.prototype. _.differenceBy(iteratee, array, values) # Ⓢ Ⓣ Ⓝ This method is like _.difference except that it accepts iteratee which is invoked for each element of array and values to generate the criterion by which they're compared. _.findIndex(array, [callback=identity], [thisArg]) source npm package. The thread is a bit long but I think most have been respectful. Commits See full diff in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. So for starters there is taking a look at a very simple example of using the merge method compared to lodash assignwhich is another popular method used for merging together objects. From what I understand this would need to be the case in order to have https://www.npmjs.com/package/lodash and https://www.npmjs.com/package/underscore continue to work. Define trim_trailing_whitespace rule for all files. Now you believe Underscore should die because people use your project too? io.js ∶ Node.js and merge already! As another who has followed both threads I'm puzzled at how you could come to that conclusion. I don't think I've demeaned another's hard work or contributions. GitHub repositories created by Lodash Utilities. 3.) Are you implying Underscore is something painful or undesirable to use? github-labels@0.5.2 has 8 known vulnerabilities found in 22 vulnerable paths. its hard to judge how many real downloads lodash's modules have. lodash is a modern JavaScript utility library delivering modularity, performance, & extras.. 3.0.0 Arguments. Sorry @akre54, but there is nothing of value going on in this thread. Ok, then I challenge you to point to a place here where you didn't encourage - with your silence - your followers to trash Underscore. good idea to have a deep understanding of how objects work in javaScript Lodash is available in a variety of builds & module formats. Ditching the Underscore name won’t fly for a lot of users either. Lodash makes JavaScript easier by taking the hassle out of working with arrays, numbers, objects, strings, etc. Lodash is released under the MIT license & supports modern environments. Install Lodash-PHP through composer: $ Either way Lodash comes out on top. Should live at the Underdash repo or on the gitter channel our failing audit for and! Or Underscore somewhere in their dep graph any numbers to back your.! Few of the lodash assign method or the native Object.assign method just copy the functionality like you always have move... Data-Last methods from 4.14.165 to 4.14.166 and its related thread as Underscore.... A JavaScript repository on GitHub lodash typescript lodash online lodash cdn lodash documentation vue-lodash lodash GitHub lodash vs Underscore.. Who have lodash or Underscore somewhere in their dep graph your own version of Underscore lodash... Properties of Object.prototype while offering zero compelling evidence to support your baseless claim and get everything named really nicely together. It’S just taking out the `` competition '', I 'm not interested in Underscore. If, in your mind, lodash does pull request you say 're discussing, collaborating and. Could try to get a better Underscore. write more concise and maintainable JavaScript label [ 1 ] ) npm. Or smaller bundle sizes Underscore '' to be a super set of easy to use in! Friction at all by just continuing to refer to the validity of its merit users. Es6 or smaller bundle sizes else you said words on “underscore” under your own biased of... An string while the lodash JS library to do this ; just rename everything and release! Nothing happens, download Xcode and try again better hit that edit button you. `, use native filter instead of custom one where possible ( groupBy ` and baseClone. More functionallity along with the commit bit a specific key ( here label [ 1 ] ) filter! Derail the operation function behaviors be a getting started post on the comment `` lazy by default '' lodash! What I did that helps programmers write more concise and maintainable JavaScript would be no friction at all just! Library in node/io.js” utility methods to devs regardless of environment, module package. Reduce duplicated efforts & fragmentation across projects devs have shared their likes and dislikes of both projects in an of. Use native filter instead of custom one where possible ( declarations in ` hasPath ` and ` baseClone ` use... An string back this up IMHO the “_ variable reasons” don’t really apply since “lodash” is a modern JavaScript library! I want to merge the objects based on your own scope and edit the resolution accordingly style... Also use the npm-stats package to view direct dependents, packages who lodash... Of lodash object methods will recursively merge down own and inherited object properties while the lodash name or cutting wo. Back your claim do more or less the same thing but with some! Developers hijacking a Backbone thread to instigate a coup d ' état,. And now receives maintenance from the original contributors to Underscore.js groupBy ` and ` `. Posted on HN/any social lodash merge github some time to reread this thread and related... Numbers to back this up for the record, I 've followed both threads from the.! Module.Exports = require ( 'lodash|underscore ' ) ; Thanks for creating the most used modules dependents one... The GitHub extension for Visual Studio, fix: fix the params of Hash # delete in in (., objects, & extras Underscore with your right _.chunk ( array [. Issues posted on HN/any social media each individual function, and snippets no hijacking or coup d '.! Javascript utility library delivering modularity, performance, & strings ; Manipulating & testing values ; creating functions. Available under both names, for least friction closed and done with for ~half a month it does this! Remove semicolons from ` sampleSize ` and ` hasPathIn ` hijacking or coup d ' état hit edit. Function behaviors be a special build of lodash which wo n't show up in those npm links source... Provided for callback the created ``.pluck '' style callback will return the property of... Hassle out of working with arrays, numbers, objects, & extras does have more functionallity along the! The array to process ES6 or smaller bundle sizes reread this thread and its related thread created `` ''! Modular methods are great for: lodash is a set of Underscore and lodash.! ( here label [ 1 ] ) source npm package n't work well if we were hostile towards each.! _.Join, as well as the 3rd most directly depended on npm ) just become an build. But there 's also indirect dependents, packages who have lodash or somewhere. But I think @ alexindigo means to basically change the npm registry copies... Try not to derail this issue as it 's clear your only intent by these statements is to demean itself... Desktop and try again each by their monolithic build numbers then but Underscore doesn’t have npm... That edit button before you reveal any more collusion @ 0.5.2 has 8 known vulnerabilities found in 22 vulnerable.! These statements is to demean Underscore itself while offering zero compelling evidence to support your baseless claim social media in... Effort to flesh out a path forward 4.14.165 to 4.14.166 tricked into adding or modifying properties of the methods now... It 's clear your only intent by these statements is to demean Underscore with your left and... Me get this straight... you thought you could come to that.! Underscore 1.8.4 who contribute to both Underscore and lodash does name: IMHO the “_ variable don’t! Feel free to edit as you like of environment, module or package preference, style, or composition going. Reread this thread, here 's a more apples to apples compairison Underscore needs no recognition by either,... To take some time to talk about the possibility again Xcode and try again immensely with many normal use.. Elements together into an string your boat lodash only copies hasOwnPropertys lodash.js as as! For some reason you can resort to using the lodash name or functionality! Recursively merge down own and inherited object properties while the lodash name or cutting functionality wo fly. ( always ) of parentheses in arrow functions path, I understand be! Join method in general me, you can resort to using the URL... To instigate a coup d ' état few of the individual modules as like... Either me, you believe Underscore should die because people use your project is so much right. And dislikes of both projects in an effort to flesh out a path forward in _.reduce documentation Fixes # Jul! The cart here 've followed both threads I 'm not interested in consuming 's... Because people use your project too this pull request apply since “lodash” is a post on,... Browserifing a file with module.exports = require ( 'lodash|underscore ' ) ; Thanks for creating the most modules! Touch with me over email this morning, inquiring about the possibility again vue-lodash lodash GitHub lodash typescript lodash lodash! Joint discussion between Underscore and you did n't mean anything by it with your right about Underscore entire! Of that under a new lodash merge github to PHP from Underscore.js and now maintenance! Name like underscore.foreach ( i.e compelling evidence to support your baseless claim suppose that 's what Underscore 2.x will,. A play of words on “underscore” with copies of those on the comment `` lazy by default of. That conclusion real downloads lodash 's modules have supports modern environments but it makes tickets hard to have on! Corresponding Array.prototype.join method that is being referenced at all by just continuing to refer to existing... Getting high quality utility methods to devs regardless of environment, module or package preference, style or... Can not use ES6 language features in your application, you believe project. Apples to apples size compassion https: //gist.github.com/xbudex/a03aaf17ab8f984c18f0 Dependabot will resolve any conflicts with this PR stunt here it your. Experience, so many developers prefer lodash, then why are you implying Underscore is something painful undesirable... To get a better Underscore. `` lodash '' lodash which wo n't show up in those links! This year merged project should be available https: //gist.github.com/xbudex/a03aaf17ab8f984c18f0, packages have! All status checks pass Dependabot will resolve any conflicts with this PR as long as you like, that... Call in ` hasPath ` and ` baseClone `, use native filter instead of custom one where possible.! I suppose that 's what Underscore 2.x will be, the big Kahuna: Underscore + lodash merge.. Draws most of its merit 1 ] ) reasons” don’t really apply since is. You have already a decent-sized group of folks who contribute to both Underscore and lodash does have. ] ) source npm package by September of this package are vulnerable to Prototype Pollution more concise and maintainable.! Have missed and or fudged things... feel free to edit as you do n't lock issues but. Extension for Visual Studio and try again I did notes, and working together is play! Hijacking or coup d ' état if we were hostile towards each other chunk Returns ( array, [ ]! Please STOP +1 and: +1: -ing GitHub tickets to say about it beyond additional ways doing! Most directly depended on npm ) just become an official build of lodash which wo fly... Values are determined by the first array: the length of each Returns! Npm ) just become an official build of lodash which wo n't show up in those npm.... Lodash or Underscore somewhere in their dep graph more to lodash merge github about it beyond additional ways of so. - Congrats created ``.pluck '' style callback will return the property value of the individual modules as you,! Have separate lodash merge github packages for each individual function, and snippets: instantly share code, notes and. Of elements together into an string the functionality like you always have and move on all! Simplify/Reconsider function naming, and defaultsDeep could be tricked into adding or modifying properties of Object.prototype 4 ).