just VS proposal-record-tuple

just-diff

You can roll your own or use a utility library. A simple zero-dependency library would be something like just-group-by [1]. Although I now prefer remeda [2] as it seems to have the best typescript support, especially the strict variants such as `grouBy.strict`.

[1] https://github.com/angus-c/just#just-group-by

Tree-shaking doesn't help much when the tree-shaken implementation is so bloated.

Here's the one you referenced, lodash.chunk: https://unpkg.com/lodash.chunk – 140 lines after removing comments and whitespace.

That's pretty small compared to a lot of the lodash utilities. Try spot-checking a few on unpkg.

I prefer angus's `just` utilities: https://github.com/angus-c/just

I absolutely love this. When I need some Lodash alternative I'll usually reference angus-c/just but I am definitely bookmarking this for next time.

The just set of utility functions are really nice to use. https://github.com/angus-c/just

Just doesn't have everything but it's pretty good

One of my favourite "libraries" are the "just" packages, where each part of the library is it's own simple package with zero dependencies (https://github.com/angus-c/just) so you essentially just npm install the specific thing you want - which is generally a single function.

If the code should, as you say, be 5 lines, why take on a dependency at all? By doing so, you end up with a catch-all solution that does almost nothing other than JSON.stringify your args, which is extremely poorly optimized to handle many situations, e.g. one of your args is a primitive and the other is a large config object.

relevant issue, which is at the crux of this problem: https://github.com/tc39/proposal-record-tuple/issues/387

There are still so many basic things that aren't in the JS stdlib, though. A good example is Map - if you need to use a tuple of two values as a key, you're SOL because there's no way to customize key comparisons. Hopefully we'll get https://tc39.es/proposal-record-tuple/ eventually, but meanwhile languages ranging from C++ to Java to Python have had some sensible way to do this for over 20 years now.

If you’re reaching for structuredClone, what you really want is native immutable Record and Tuple syntax, and the companion “deep path properties” syntax which allows for efficient and ergonomic immutable updates:

- https://github.com/tc39/proposal-record-tuple

It will be called "record" in JavaScript which will swing the popularity back the other way I guess (currently a language proposal)

I suspect considering the strong desire to maintain consistency with JavaScript, we will eventually see something that when the Record proposal passes through tc39

I hope the Record and Tuple proposal makes it through

I mean, I'd love some real immutable/persistent data structures in JS by default, or even some Immer-like syntax sugar. Something like the record/tuple proposal would be awesome.

This will become very useful once Records and Tuples are a thing, because it allows you to store object references in a record/tuple (which by definition can only contain primitives).

Record and tuple is at stage 2

Also, js has an ongoing immutable value data types proposal.