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-app-perf-lighthouse

v0.0.10

Published

A script to run your local web app and yield developer experience and user performance data

Downloads

1

Readme

node-web-app-perf-lighthouse

A script to run your local web app and yield developer experience and user performance data

This script is a drop in to perform the following in most Node.js based-web apps:

  • count the vulnerabilities
  • count the number of production node_modules
  • count the number of total node_modules
  • measure the installation time of npm ci (no node_modules)
  • run lighthouse programmatically, using npm run serve, gathering standard web vitals data
  • reports diagnostic data like the number of request, total bytes, etc
  • measures the build time of the app using npm run build

There seem to be a lot of tools that ALMOST do this, but a use case here is to run this vs different SHAs of your own site to compare results over time. No one metric tells the complete story, so be aware of the tradeoffs you make.

Installation

  1. Drop audit.mjs into your web app.

Usage

  1. Configure an .env file :
    HOST = 'http://localhost'
    PORT = ':3000'
    PATH = '/en'
    VERBOSE = true
    INSTALL = true
    FILESIZE = true
    WRITE = true
    MS_WAIT_BEFORE_LIGHTHOUSE = 10000
  2. Run node audit.mjs
  3. Review ./audit-report.json

Sample Output:

{
  "vulnerabilities": 22,
  "prodNodeModulesCount": 233,
  "prodNodeModulesSize": "40M",
  "allNodeModulesCount": 728,
  "allNodeModulesSize": "130M",
  "installTimeResult": "7s",
  "lightHouseTestResults": {
    "first-contentful-paint": "2.3 s",
    "largest-contentful-paint": "2.3 s",
    "first-meaningful-paint": "2.3 s",
    "speed-index": "2.3 s",
    "total-blocking-time": "0 ms",
    "max-potential-fid": "20 ms",
    "cumulative-layout-shift": "0.041",
    "interactive": "2.3 s",
    "server-response-time": "Root document took 10 ms",
    "bootup-time": "0.1 s"
  },
  "diagnosticPropertyResults": {
    "numRequests": 12,
    "numScripts": 3,
    "numStylesheets": 3,
    "numFonts": 1,
    "totalByteWeight": 75421
  },
  "elapsedBuildTime": "9.873"
}