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

overlooker-element-timing

v0.2.4

Published

The package for measuring the element timing is more simple

Downloads

77

Readme

overlooker-element-timing

Build Status npm overlooker-element-timing package

Install

npm i overlooker-element-timing

Usage

Adding the Overlooker Element Timing is a two-step process. First you need to add a snippet of code to the head of your document (before any other scripts run). This snippet creates a PerformanceObserver instance and starts observing element entry types.

if (!window.oet) {window.oet = [];}if (PerformanceObserver) {new PerformanceObserver(function (l) {window.oet.push.apply(window.oet, l.getEntries());}).observe({ entryTypes: ['element'] });}

Note: You can use something else instead of oet, but you should put this string in the OverlookerElementTiming constructor as the first argument.

Second step is to import the module in your application and subscribe to it

import OverlookerElementTiming from 'overlooker-element-timing';

// you can put the name of the global variable that you used for store entries, in the first argument (default = 'oet')
const overlookerElementTiming = new OverlookerElementTiming();

overlookerElementTiming.observe((entry) => {
    // entry object contains element timing data in readable form
    // use it according to your need
}, true); // set to true, if you want to receive already handled entries; 

// for getting already handled entries
overlookerElementTiming.getAll().forEach((entry) => {
    // handle
});

Note: entry types.

If you want to use this script in embedded version (with script tag), you can put the ./dist/index.min.js anywhere and use it from global namespace

window.oet.observe(() => {
    // ...
});