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

inp-lab-test

v1.0.0

Published

Automation to run interactions on your pages multiple times therefore getting more reliable INP and TBT numbers

Downloads

13

Readme

inp-lab-test

Automation to run interactions on your pages multiple times therefore getting a more reliable INP and TBT numbers

Getting started

npm i --save-dev inp-lab-test

Create a js file with the name you want (a suggestion is pagename-interactionScenario.js) and paste the following code

const { startAutomation } = require('inp-lab-test');

const navigationCallback = async (runner) => {};

const interactionsCallback = async (runner) => {};

startAutomation({
  navigationCallback,
  interactionsCallback,
});

Then:

  • Go to your website in the page you wanna test
  • Open Chrome Devtools
  • Go to the experimental Recorder tab (it might be hidden under the 3 dots > more tools)
  • Start recording
  • Do all the interactions you want on your page
  • Stop Recording
  • Click on dowload icon (the arrow down icon)
  • Select @puppeteer/replay
  • Open the file you just downloaded
  • Copy the first 2 runner.runStep (the ones for setting viewport and navigating) and paste them inside navigationCallback
  • Copy the rest of the runner.runStep and paste them inside interactionsCallback
  • Run node yourFileName.js

API

Functions

startAutomation()

type startAutomation = (options: StartAutomationOptions) => void;

Types

PuppeteerReplayRunner

Check docs for this on puppeteer/replay repo

StartAutomationOptions

interface StartAutomationOptions {
  navigationCallback: (runner: PuppeteerReplayRunner) => {};
  interactionsCallback: (runner: PuppeteerReplayRunner) => {};
  samplesAmount?: number; // defaults to 10
  CPUThrottling?: number; // defaults to 12
  debug?: boolean; // defaults to false
}