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

@aics/frontend-insights

v0.2.3

Published

Light abstraction API on top of 3rd party monitoring tool(s).

Downloads

548

Readme

@aics/frontend-insights

Light abstraction API on top of 3rd party monitoring/metrics/analytics tool(s).

Plugins

This library is useful insofar as 3rd party services are plugged into it; without plugins, it is effectively a noop API. Plugins are given to the default export of this package, the FrontendInsights class, which acts as a dispatcher of messages to its configured plugins.

This library defines an interface that must be implemented for each 3rd party service to be usable as a plugin to FrontendInsights. The interface is intentionally as generalized as possible. That interface is:

interface FrontendInsightsPlugin {
    process(message: FrontendInsightsMessage, context: FrontendInsightsContext): void;
}

External services should be initialized (e.g., given an API key) in a plugin constructor. Thereafter, it is the decision of the plugin whether to process some, all, or no messages distributed by the FrontendInsights class. For example, a plugin that works entirely by monkeypatching the browser's window.onerror event (as some browser-based exception monitoring services do), might choose to not process any messages. An analytics service, on the other hand, might choose to process FrontendInsightsMessageType.UserEvent and FrontendInsightsMessageType.UserTiming messages.

Additional plugins and message types may be added as necessary with no concern to existing usages of the library. If a new message type (FrontendInsightsMessageType) is added, it is recommended to add a specific public method to FrontendInsights for dispatching that type of message, similar to FrontendInsights::dispatchUserEvent.

Usage

import FrontendInsights, { FrontendInsightsContext } from "@aics/frontend-insights";
import AmplitudeNodePlugin from "@aics/frontend-insights-plugin-amplitude-node";

const context: FrontendInsightsContext = {
    application: {
        name: APP_ID,
        version: "4.2.2",
    },
    userInfo: {
        userId: "[email protected]",
    },
    session: {
        platform: "Electron"
    }
};
const frontendInsights = new FrontendInsights(context, [
    new AmplitudeNodePlugin({ apiKey: "abc123" }),
    new WhateverPlugin({ ... }),  // e.g., could be others...
]);

frontendInsights.dispatchUserEvent({
    type: "ANY_STRING",
    properties: {
        foo: true,
        bar: "no",
        baz: 123,
    },
});