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

jsfperf

v1.1.0

Published

expoerimenting with performance metrics between multiple fp libraries

Downloads

3

Readme

jsFPerf

Build Status

To see the latest results, check the travis build.

Lots of talk about which immutable solution is faster and for what.

I made this repository because I was curious what the stats would be.

Installation

npm i -g jsfperf

Usage

By default, jsfperf will run all of the available tests with small sample sizes.

if You want to alter the size of the samples, you can choose between empty, singleton, small, medium, large.

If you only want to run a subset of the tests, you can append their names to the command.

# run all tests with small samples
jsfperf

# run the find benchmark with medium samples
jsfperf -m find

# run the find and assocPath benchmarks with empty samples
jsfperf --empty find assocPath

# run all tests with large samples
jsfperf --large