_ VS lodash

Your post (and library) seem to imply that micropackages are good if they are useful (in an absolute sense), so long as they don't create excessively large dependency trees. I would argue instead that every package should be treated to a cost/benefit analysis, and it's often better to not use useful packages at all when the benefit is small. As a concrete example, your Recursion module appears to be about 20 lines of code whose value proposition is that you can now type &_ instead of &?ROUTINE (or Dbg lets you type foo(dbg($x)) instead of dd($x); foo($x)). This is (arguably) a useful thing to have, but using even this very tiny micropackage comes with costs. The first cost is that there are now 20 extra lines of external code you must trust to be bug-free, performant, maintained, and non-malicious, but there is also a cost that whoever is reading your code now has to know what &_ means, or where to look to find the answer.

After that, I agree that there should be some way to mark some sub-packages as v0.*, but I'm not quite sure what the best way to do so is. I've jotted down some initial thoughts at github/codesections/_/issues/3 and would be interested in any thoughts that you (or others) might have (warning: very rough!). I don't currently have anything in there about API numbers – I like that idea, but I'm not sure where they fit.

Lodash.js is like the Swiss Army knife for JavaScript developers. Need to manipulate data structures or dabble in functional programming? Lodash is here to save the day with its arsenal of utilities. It's all about making your code cleaner and your life easier, which is probably why big guns like Google and Airbnb have it in their toolkit.

lodash - utility library enabling things like deep object comparison that aren't easy to do with javascript out of the box. docs

Lodash is a widely used JavaScript utility library that provides a plethora of functions to simplify common programming tasks. From manipulating arrays and objects to handling edge cases and implementing functional programming paradigms, Lodash offers a comprehensive toolkit for JavaScript developers. In this beginner's guide, we'll learn how to get started with Lodash and leverage its functionality to write cleaner, more efficient, and more maintainable code.

5. Lodash

If you want even more sophisticated equality checks like deep comparisons, there's the: lodash.iseQual library that'll do this for you out of the box. At least now you do have a bit of clarity on what's happening under the hood, so there's no harm in using a library.

It's also important to ensure that you're importing libraries correctly, so webpack can perform tree shaking effectively. For example, let's import lodash, as follows:

Lodash is awesome! It’s a JavaScript library that helps you do many things with data. You can use Lodash to manipulate arrays, objects, JavaScript strings, numbers, and more. It’s easy to get Lodash in your project. You can use npm or a CDN to install and import it. Here’s how:

Think of RxJS as Lodash for events.

lodash and You Might Not Need Lodash

A lot of Lodash functions are implemented as combinations of other Lodash functions, so importing a single function actually imports half of Lodash under the hood:

https://github.com/lodash/lodash/blob/main/src/.internal/bas...