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

web-component-benchmark

v0.0.4

Published

A tool that aims to provide benchmarks for Polymer 1 and 2 web components The benchmark is simply made by measuring the time it takes to instantiate a component. It runs multiple times in order to get statiscally significant results

Downloads

3

Readme

web-component-benchmark - alpha 1

A tool that aims to provide benchmarks for Polymer 1 and 2 web components The benchmark is simply made by measuring the time it takes to instantiate a component. It runs multiple times in order to get statiscally significant results

An ASCII chart and statistics are generated

This theoretically also allows detecting memory leaks like the one on paper-input-char-counter

Installation

npm i -g web-component-benchmark

If Selenium cannot find the Chrome webdriver:

npm i -g chromedriver

Example

wcb -c src/my-component.html

Usage

  -o, --output string         Save the results to a JSON file                                               
  --runs number               Number of times the harness run (defaults to 10)                              
  --times number              Number of times the element is instantiated per harness run (defaults to 100) 
  --baseline string           Base native HTML tag against which performence will be measured (defaults to  
                              input)                                                                        
  -c, --components string[]   Which components you want to benchmark (defaults to the content of bower.json 
                              "main" entry)                                                                 
  --hub string                Remote selenium hub address (leave empty for local)                           
  -q, --quiet                 Silence output                                                                
  --root string               Root of the project (defaults to current location)                            
  -p, --path string           Path to the component (defaults to current location)                          
  -v, --verbose               Verbose mode                                                                  
  -h, --help                  This page 

Future releases

This is still an alpha tool, multiple issues are still to be solved:

  • Support Polymer 3 as well as vanilla components and lit elements
  • Support IE11, Edge, Firefox, Safari and Opera
  • Pass the benchmark runner and its dependencies as a data/html string instead of copying them over and removing them
  • Tests!
  • I'm currently considering regression testing for use in a CI environment

Help and feature requests are very welcome