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

@fw-components/trackers

v2.0.6

Published

Usage trackers for web components

Downloads

229

Readme

@fundwave/trackers

A utility that traverses the DOM and registers listeners to elements (even those present within shadowDOMs) from a provided list of events that are to be tracked.

1. How it works

The consumer can either provide a store configuration and the events will be fetched and parsed from the store or an array of events to be tracked.

Schema of an event-config:

{
  "jsPath": "document.querySelector...",
  "location": "/dashboard", // glob pattern of the url where the target-element is to be tracked
  "title": "Clicked at dashboard edit-button",
  "event": "click" // type of event | All js events are supported
}

2. Usage

const tracker = new Trackers({
  store: {
    type: "notion",
    context: {
      url: "URL_TO_RETRIEVE_NOTION_DB",
      pageId: "<<PAGE_ID>>",
    },
  },
  track: yourTrackingMethod,
  debug: true,
});

tracker.initialize();

Note:

tracking multiple targets is also supported. Use :nth-child(+) identifier to highlight elements whose multiple instances are to be tracked

Supported selector

document.querySelector("div > div.main-content > div.page > route-page > request-grid:nth-child(+)")