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-profiler

v0.1.3

Published

A very detailed profiler and e2e regression testing tool for web apps

Downloads

22

Readme

Web Profiler

Build Status

This project has three main goals:

  • profiling the speed of single pages along a prefixed flow, with very detailed timings that will allow to spot infrastructure problems. Pretty much tries to answer to users saying "It's slow"
  • regression testing (with very simple checks for now)
  • pre-flight checklist. Another take on regression testing

For now everything relies on a very primitive scenario file for which you find an example in the scenarios folder. The format is almost self explanatory. Some documentation will follow.

All the steps are performed serially. This is by design. The client is configured to keep a cookie-jar in order to act as an authenticated user against a regular session. Some very peculiar choiches (especially regarding form POSTing) account for the intricacies of ez-publish legacy. More on this in a later version

docker build -t web-profiler
docker run -v ./scenarios/:/scenarios -e "scenario=/scenarios/scenario_1.json" --rm marco/web-profiler | pino-pretty