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

rino

v0.1.1

Published

Simple and accurate website load testing and analysis

Downloads

4

Readme

rino

npm npm npm

Simple and accurate website load testing and analysis

Installation

npm install --save rino

Usage

    // somefile.js
    var rino = require('rino');


    rino('siwiec.us', 200)
    // to run metrics + a 200 http request benchmark

    rino('siwiec.us')
    // to run metrics + a default 100 http request benchmark

When run, this code will: 1. Produce two files in the same directory as the code named benchmark.json and size.json. 2. Populate those files with information collected from those files

Example files

Note: these files were run with rino('siwiec.us', 100) and units are in seconds

benchmark.json:

{
    "results": [
        0.74,
        0.75,
        0.75,
        0.75,
        0.76,
        0.78,
        0.78,
        0.79,
        0.79,
        0.79,
        0.79,
        0.79,
        0.79,
        // And so on
    ],
    "totalTime": "2.49",
    "mean": "1.47",
    "median": 1.585
}

size.json:

{
    "id": "https://siwiec.us/",
    "responseCode": 200,
    "title": "Adam Siwiec - Full Stack Developer",
    "ruleGroups": {
        "SPEED": {
            "score": 91
        },
        "USABILITY": {
            "score": 100
        }
    },
    "pageStats": {
        "numberResources": 16,
        "numberHosts": 4,
        "totalRequestBytes": "1591",
        "numberStaticResources": 10,
        "htmlResponseBytes": "12053",
        "cssResponseBytes": "1018",
        "imageResponseBytes": "199903",
        "javascriptResponseBytes": "303899",
        "otherResponseBytes": "43161",
        "numberJsResources": 2,
        "numberCssResources": 1
    },
    "totalSize": "562 kB"
}

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

History

I wanted some solid, consistent data from some of the websites so I could compare different providers speeds. I couldn't find an all-in-one, simple, no-setup option, so I created my own. Tada it's rino!

Credits

Todo:

* Have the json files be returned as objects in code
* Create a cli

Licensed under the MIT License