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

@ganesh-40/vizme

v1.0.3

Published

Unified visibility platform - This is the library that was built for visualizing the metrices, which would be made open-source to public.

Downloads

20

Readme

Vizme - Unified Visibility Platform

A lightweight JavaScript library for tracking metrics to your unified visibility platform.

Installation

npm install @ganesh/vizme

The package is published under the @ganesh scope on npm (public). Use this scoped name; the unscoped name vizme is blocked by npm (similarity with other packages).

Package entry points

| Use case | Import / path | |----------|----------------| | Bundlers (Vite, Webpack, etc.) | import Vizme from '@ganesh/vizme' (ESM) or const { Vizme } = require('@ganesh/vizme') / require('@ganesh/vizme').default (CJS) | | Script tag (no bundler) | Copy or serve node_modules/@ganesh/vizme/dist/vizme.js; exposes window.Vizme |

Quick Start

Browser (bundler)

import Vizme from '@ganesh/vizme';

// Initialize
const tracker = new Vizme({
  apiKey: 'mk_your_api_key_here',
  endpoint: 'http://localhost:3000/api/v1/metrics',
  autoTrack: true // Automatically track page views, errors, performance
});

// Make it globally available
window.vizme = tracker;

// Track custom events
window.vizme.increment('add_to_cart', 1, {
  product_id: '123',
  product_name: 'Product Name'
});

Browser (script tag, no bundler)

Serve or copy node_modules/@ganesh/vizme/dist/vizme.js and include:

<script src="/path/to/vizme.js"></script>
<script>
  window.vizme = new Vizme({
    apiKey: 'mk_your_api_key_here',
    endpoint: 'https://api.example.com/api/v1/metrics',
    autoTrack: true
  });
</script>

Vizme is available as window.Vizme after the script loads.

HTML Attributes (Zero Code)

<button 
  data-vizme-track="add_to_cart"
  data-vizme-value="1"
  data-vizme-label-product-id="123">
  Add to Cart
</button>

API

track(name, value, labels)

Track any metric with a value.

increment(name, value, labels)

Increment a counter metric.

decrement(name, value, labels)

Decrement a gauge metric.

set(name, value, labels)

Set a gauge metric value.

flush()

Force immediate send of batched metrics.

getStatus()

Get current status (queue size, batch size, etc.).

Auto-Tracking

When autoTrack: true, the library automatically tracks:

  • Page views
  • Page load time
  • JavaScript errors
  • Web Vitals (FCP, LCP, FID, CLS)
  • Scroll depth
  • Time on page

Publishing (maintainers)

  1. Scope: The package name is @ganesh/vizme. Your npm user must match the scope (ganesh) or you must be a member of the @ganesh org with publish access.
  2. Rename: To publish under a different user/org, change "name" in package.json to @your-npm-username/vizme, then run npm publish from library/ (publishConfig.access is already public).
  3. Login: npm login and npm whoami before publishing.

License

MIT