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

dom-event-tracker

v1.3.3

Published

Dynamically tracks mutations and listens for click and seen events

Downloads

69

Readme

🚀 Dom Event Tracker!

Dynamically tracks mutations and listens for click and seen events.

CircleCI codecov npm version

DOM Event Tracker uses IntersectionObserver and MutationObserver for tracking click and seen events. Whenever an element is visible in the users screen it fires seen event. Whenever user clicks an item, it fies click event.

Install

npm install dom-event-tracker

Custom Build

You can also clone repository and build.

git clone [email protected]:Trendyol/dom-event-tracker.git && cd dom-event-tracker
npm install
npm run build

Usage

  1. Add data-tracker-root attribute to root element. Root element is being tracked for mutations.
  2. Add tracking attributes to elements that you want to track data-tracker="seen:seenEventName click:clickEventName".
  3. Start Tracker
window.Tracker.init((eventName, eventType, element) => {
    //Report your event
    GoogleAnalytics.fireEvent(eventName);
});

Example

<html>
    <head></head>
    <body>
        <div class="container" data-tracker-root>
            <div>
                <div class="info-box" data-tracker="seen:infoBoxSeen"></div>
            </div>
            <div class="help-button" data-tracker="click:helpButtonClicked"></div>
            <div class="info-button" data-tracker="click-capture:infoButtonClicked"></div>
        </div>
        <script>
            window.Tracker.init(); // Without callback it uses console for notifying events
        </script>
    </body>
</html>

Event Types

Seen (seen:eventName)

Whenever an element is visible in the users screen it fires seen event. IntersectionObserver without threshold.

Whenever callback returns true, seen event won't be fired for that element. Otherwise it will always fire seen event. This means almost each scroll

Click (click:eventName)

Whenever user clicks an item, it fires click event. Uses event bubbling for listening click events.

ClickCapture (click-capture:eventName)

Whenever user clicks an item, it fires click event. Uses event capturing for listening click events.

Tracker Callback

Root Callback

You can provide root callback for async initialize.

<div data-tracker-root="onTrackerLoaded">
    <div data-tracker="seen:seenItem"></div>
</div>
<script>
function onTrackerLoaded(e){
  GoogleAnalytics.event(e);
}
</script>
<script src="cdn://tracker.min.js" defer></script>

Custom start

You can also call init manually

<div data-tracker-root="">
    <div data-tracker="seen:seenItem"></div>
</div>
<script src="cdn://tracker.min.js"></script>
<script>
    window.Tracker.init((e) => GoogleAnalytics.event(e));
</script>

Callback Params

function callbackHandler(eventName, eventType, element){
  
}