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

@firebase-me/tracker

v1.0.1

Published

A firebase database tracker

Downloads

3

Readme

*Alpha v0.1 This is a Firebase Usage Tracker, it is designed to to capture snapshots from firebase calls to Firestore and Realtime, Storage is not functional at this current time.

The package uses the REST API to reduce any potential overhead

to Use:

import tracker from '@firebase-me/tracker';

tracker.init(databaseUrl, auth?(optional), ping?(optional))
  • databaseURL is the realtime database url from your web credentials
  • auth - optional - only needed when initiating after the user is declared
  • ping - optional - only valid if a current auth object is processed

when the user state changes, the user auth object needs to be updated:

onAuthStateChanged(user){
    tracker.updateAuth(user)
}

If you are not using the web modules; the only required fields are the user UID and the ID token for authenticating the request. you can pass it as the user object as such {uid:"userUID", idToken:"ID token Credential"}

There are 3 ways we intend to allow users to utilize this suite: 1: Pass the snapshot from the request into the appropriate tracker method and it will update to the appropriate realtime DB. 2: Assign a custom callback function via: tracker.<service>.setCallback(myFuntion) which expects a single parameter payload(3) 3: If no callback(2) is assigned and the tracker has not been initialized: it will simply return the payload as a JSON object so you can handle it through a console log, custom integration, etc.

To use the trigger to log each respective database type:

// Firestore
tracker.firestore.trigger(snapshot|data, meta?, customPath?)
// Realtime DB
tracker.realtime.trigger(snapshot|data, meta?, customPath?)
// Storage (not implimented)
// tracker.storage.trigger(snapshot|data, meta?, customPath?)
// Custom Meta
tracker.meta.trigger(payloadObject|data, meta?, customPath?)

Each snapshot is evaluated, Firestore as Documents (supports cached tracking) Realtime DB is evaluated as Bytes and rounded to the nearest KB Meta uses the same as Realtime. Each trigger also supports custom path overrides, allowing you to define assign the snapshot path as a unique path independant of their original reference path. This can be used for custom filtering and targeting.

Standard payload:

{
    time: timestamp,
    auth: string | null,
    path: string | null,
    size: number | null,
    cache: number | null, // firestore only
    meta: string | null,
}

Storage is not functional at this time, please do not use it as it will most likely throw errors.