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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@e-llm-studio/click-tracking

v0.2.1

Published

Shared click-tracking protocol and React helpers for BPA host and remote applications.

Downloads

97

Readme

@e-llm-studio/click-tracking

Shared protocol, React helpers, and host-side delivery tools for click and functionality tracking. Authentication, runtime URLs, and product-specific event catalogs are injected by the consuming application.

import { RemoteTracker, useRemoteTracker } from '@e-llm-studio/click-tracking/react';

function Content() {
  const tracker = useRemoteTracker();
  return <button {...tracker.attributes('save_clicked')}>Save</button>;
}

export function Mode() {
  return <RemoteTracker mode="Example Mode"><Content /></RemoteTracker>;
}

By default, events use window.hostMicroFrontendApi.dispatch. A remote can instead pass an explicit dispatch function or dispatch-capable object to RemoteTracker/createRemoteTracker.

Keep mode and feature names in the consuming application. Lifecycle outcomes should use metadata such as { status: 'started' | 'completed' | 'failed' } rather than separate transport implementations.

Host applications and VS Code webviews

The /host entry point contains the IndexedDB adapter, queue, activity tracking, aligned publisher, API payload builder, and feature API client. It does not import CW Core modules.

import {
  HostClickTracker,
  createHostTrackingStore,
  createIndexedDbTrackingStorage,
  createTrackingDelivery,
} from '@e-llm-studio/click-tracking/host';

const deliver = createTrackingDelivery({
  endpoint: () => `${runtimeApiUrl}/segment_click_analytics/v1/submit-ui-clicks`,
  request: extensionApiRequest,
  getUserEmail: () => currentUser.email,
  resolveMode: resolveRegisteredModeAndFeatures,
});

const store = createHostTrackingStore({
  defaultMode: 'vscode-extension',
  storage: createIndexedDbTrackingStorage({ database: 'extension-click-tracking' }),
  deliver,
});

export const App = () => (
  <HostClickTracker store={store} eventNames={['chat_used', 'file_opened']}>
    <ExtensionLayout />
  </HostClickTracker>
);

Mark the chat textarea with data-cw-track="chat_used", or call store.getState().track(...) for actions such as opening a file in the right pane.