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

@flive/react-benchmark

v0.2.0

Published

Helper to measure the performances of flive components

Downloads

6

Readme

@flive/react-benchmark

A tool for benchmarking the render performance of Flive components.

It compiles the benchmark code into a minified production bundle using Webpack and then runs it in headless Chrome to benchmark the real production code in a real production environment.

Note: the benchmark numbers aren՚t completely accurate and should only be used relatively to compare the performance difference of code changes or different implementations.

To have a reliable test, run it without any heavy process that could parasitize the results.

Usage

const pkg = require('../package.json');

const Benchmark = new ReactBenchmark({ pkg });

Benchmark.render([
  {
    name: 'My component description',
    filepath: path.join(path.resolve(), 'benchmark/tests/MyComponent.js')
  },
  ...
]);

Output

Table of component tests

| Component name | Test | Test without styled primitives | Gap | | -------------------------- | --------------------------------------- | -------------------------------------- | ------ | | My component 1 description | 98.75 ops/sec ±16.59% (43 runs sampled) | 136 ops/sec ±1.84% (42 runs sampled) | 27.56% | | My component 2 description | 22.91 ops/sec ±22.95% (37 runs sampled) | 44.52 ops/sec ±5.72% (38 runs sampled) | 48.55% |