Compatibility table

This table puts equivalent NoDash, Underscore, LoDash and ECMAScript’s functions side by side, noting their differences where applicable.

Green cells mark functions supported by NoDash and by one of the other libraries.

footnote1Underscore’s un:flatten() defaults to depth of Infinity while LoDash’s lo:flatten() and ES’ flat() proposal (and NoDash’s flat()) – to depth of 1.

footnote2NoDash’s template() syntax is not based on <%ERB%> but on {{Mustache.js}}.

footnote3sq:Sqimitive\Core::masker() provides a similar functionality.

footnote4sq:Sqimitive\Ordered::indexFor() provides a similar functionality.

footnote5Exists in Underscore.String: https://github.com/epeli/underscore.string/

footnote6Not supported natively in any version of Internet Explorer.

footnote7sq:Sqimitive\Core::unique() provides a similar functionality (but doesn’t prepend prefix to the result).

footnote8NoDash’s invoke() and Underscore’s un:invoke() call a method on every object in an array parameter while LoDash’s lo:invoke() accepts a single object and calls a method on it.

footnote9sq:Sqimitive\Core::stub() is the same.

footnote10Underscore’s un:mixin() extends Underscore’s own functionality. LoDash’s lo:mixIn() is similar to sq:Sqimitive\Core::mixIn().

footnote11Use instanceof to check for these types. For example: /0.*/ instanceof RegExp.

footnote12Underscore’s un:isEqual() and LoDash’s lo:isEqual() are very elaborate. NoDash simply defers to == so in NoDash _.isEqual([], []) === false while _.isEqual([], '') === true.

footnote13sq:Sqimitive\Core::deepClone() and sq:Sqimitive\Core::deepCloner() (compiled version thereof) provide a similar functionality.

footnote14NoDash’s ajax() semantics is very similar to jQuery’s ajax().

footnote15sq:Sqimitive\Core::picker() provides a similar functionality.

footnote16NoDash’s once() can be used like un:memoize()/lo:memoize() with dumb hashFunction/resolver, returning the same cached value regardless of arguments.

footnote17LoDash’s lo:at() supports complex string path notation (a[0].b.c).

footnote18LoDash’s lo:property() supports complex string path notation (a[0].b.c) while in NoDash’s property() and Underscore’s un:property() a string stands for a single key.

footnote19LoDash’s lo:flip() is very different: it wraps a function, inverting its argument order.

footnote20Do not confuse escape() with the native o:escape() function used for URL encoding.

footnote21Underscore’s un:object() combines NoDash’s object() (takes two lists: keys and values) and fromEntries() (takes one list: key-value pairs).

footnote22NoDash’s bind() recognizes undefined context to keep caller-provided this while Underscore’s and LoDash’s assume globalThis, like window.

Underscore’s un:partial() and LoDash’s lo:partial() support placeholder arguments (_) but bind() doesn’t, so partial() alias is not fully compatible.

footnote23Used to exist in Underscore.String: https://github.com/epeli/underscore.string/, was deprecated in favour of https://npmjs.org/package/sprintf-js.