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

piral-tracker

v1.5.4

Published

Plugin for registering always-on components in Piral.

Downloads

951

Readme

Piral Logo

Piral Tracker · GitHub License npm version tested with jest Community Chat

This is plugin that only has a peer dependency to piral-core. What piral-tracker brings to the table is a set of Pilet API extensions that can be used with piral or piral-core.

Why and When

Sometimes you want to register components that should always be active, e.g., for reporting purposes, to show up periodically, or to make certain validations. Either way, out of the box you could do that via some extension, but a more convenient way to integrate such a component could be via a dedicated API.

This plugin gives you such an API and a ready-to-use component that you can integrate on all pages (or maybe even in your layout) where these registered trackers should be active.

Documentation

The following functions are brought to the Pilet API.

registerTracker()

Adds the definition of a tracker to the app shell.

If the first argument is a string a named tracker is registered. A named tracker can also be removed.

unregisterTracker()

Removes a tracker from the app shell. This requires a named tracker.

Usage

::: summary: For pilet authors

You can use the registerTracker function from the Pilet API to add a new tracker in the app shell.

Note: When the first argument is a string we call it a named tracker.

Example use:

import { PiletApi } from '<name-of-piral-instance>';

const MyTracker = () => {
  return null;
};

export function setup(piral: PiletApi) {
  // 👇 Registers a named tracker called "my-tracker"
  piral.registerTracker('my-tracker', MyTracker);

  // 👇 Registers an anonymous tracker
  piral.registerTracker(MyTracker);
}

You can use the unregisterTracker function from the Pilet API to remove a previously added tracker from the app shell.

Note: You'll need to have added a named tracker in order to be able to remove it.

Example use:

import { PiletApi } from '<name-of-piral-instance>';
import { MyTracker } from './MyTracker';

export function setup(piral: PiletApi) {
  // register with a name
  piral.registerTracker('first', MyTracker);
  // and unregister; maybe some time later?
  piral.unregisterTracker('first');
}

:::

::: summary: For Piral instance developers

The provided library only brings API extensions for pilets to a Piral instance.

For the setup of the library itself you'll need to import createTrackerApi from the piral-tracker package.

import { createTrackerApi } from 'piral-tracker';

The integration looks like:

const instance = createInstance({
  // important part
  plugins: [createTrackerApi()],
  // ...
});

:::

License

Piral is released using the MIT license. For more information see the license file.