npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

vanillas

v1.10.0

Published

Dependency-free, low-level JavaScript function helpers

Downloads

1,485

Readme

Vanillas

JavaScript utility functions. Comparable to Lodash or Ramda, but faster. In some cases it even outperforms native implementations (or leverages native implementations that are messy to type out).

Why Another Utils Lib?

Lodash/Underscore created an API many years ago which is unfavorable to Currying. For currying to be possible you need the final argument to your function to be the data on which you operate (rather than the first arg). And although Lodash/Underscore has an "fp" (functional programming) subset, the fundamental flaw in the argument order can't be corrected.

A similar utils library Ramda was created as a classic functional programming library, and the most notable change was to reorder the arguments to be favorable to currying. Ramda took it a step further than than (perhaps too far) of making every function in the whole library curried. This isn't always desired. But the more critical flaw with Ramda is it is slow. Very slow.

Vanillas was created to correct those perceived flaws in both Lodash/Underscore and Ramda. It outperforms those libraries, makes currying possible, yet allows you to opt-in to currying.

Docs

View the full docs. These are generated from - and always in-sync with - the JsDoc code annotations.

Curried vs Non-Curried

Importing from the root vanillas namespace yields all the non-curried utility functions (including the curry() function itself if you want to do your own). To use the curried versions of the Vanillas utility functions though, just import from the vanillas/curried directory rather than from the root.

Installation

npm install vanillas

Benchmarks

Run any of the files in the benchmark/test/ directory.

Examples (run one or more benchmark tests, space-delimited):

npm run benchmark compose
npm run benchmark propAt
npm run benchmark mapObject
npm run benchmark compose mapObject propAt

Or you can run all of them (grab a cup of coffee while you wait):

npm run benchmark

View Current Benchmarks