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

page-performance-metrics

v1.2.1

Published

Measures loading time of a page across many microfrontend modules.

Downloads

1,225

Readme

Page performance metrics

Measures loading time of a page across many microfrontend modules.

A page should mark it's finished loading time as soon as the main data is loaded and the user can start working with it.

E.g. for a page which contains some quick info (which can be edited) and also a big report (which takes long to load, but it's ok that it takes longer) the page should mark it's ready state when the quick data arrives.

Install

npm i page-performance-metrics

How does it work?

Using a hook the page marks the start time of it's rendering. In the same step the page defines which marker tags should be set in order to mark the page as ready.

This only works if all components define this module as peerDependency and built together in a final build step.

Here is an example:

import { markPerformanceTag, usePagePerfMetrics } from "page-performance-metrics"
import { OtherMicroFrontendComponent } from 'other-client-package'

async function loadSomeData() {
  return new Promise(resolve => {
    setTimeout(
      () => {
        // mark the data loading as finished
        markPerformanceTag('coolApp/superCoolPage/data')
        resolve('this is real data')
      },
      1000
    )
  })
}

const SuperCoolPage = () => {
  // mark point in time and needed tags for the performance measurement
  usePagePerfMetrics({
    pageName: 'coolApp/superCoolPage',
    tagList: [
      'coolApp/superCoolPage/data',
      'otherMicroFrontendComponent/data',
    ],
  })

  const [data, setData] = useState(null)
  useEffect(() => {
    loadsomeData().then(setData)
  }, [])

  return (<div>
    <span>
      This is the loaded data: {data}
    </span>
    { /* This component will send out the other tag from the tagList */}
    <OtherMicroFrontendComponent>
  </div>)
}