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

@amplifyup/sdk

v0.1.1

Published

AmplifyUp Tracking SDK - CDP-agnostic event tracking library

Readme

@amplifyup/sdk

AmplifyUp Tracking SDK - CDP-agnostic event tracking library.

Overview

This SDK provides event tracking that sends events directly to AWS API Gateway. All URLs are hardcoded in the SDK - no configuration needed except trackingId.

Installation

npm install @amplifyup/sdk

Usage

Basic Setup

import { init } from '@amplifyup/sdk';

// Initialize the SDK (URLs are hardcoded)
await init({
  trackingId: 'your-tracking-id',
  debug: true, // Optional, enables debug logging
});

Track Events

import { 
  page, 
  track, 
  trackClick, 
  trackFormSubmit,
  trackContentView,
  identify 
} from '@amplifyup/sdk';

// Track page view
page('/home');

// Track custom event
track('Product Viewed', {
  productId: '123',
  productName: 'Widget',
  price: 29.99
});

// Track button click
trackClick('add-to-cart', 'Add to Cart', {
  productId: '123'
});

// Track form submission
trackFormSubmit('newsletter-signup', {
  email: '[email protected]'
});

// Track content view
trackContentView('product-123', 'product', {
  productName: 'Widget',
  category: 'Electronics'
});

// Identify user
identify('user-123', {
  email: '[email protected]',
  name: 'John Doe'
});

Get Instance ID

import { getInstanceId } from '@amplifyup/sdk';

const instanceId = getInstanceId();

Architecture

The SDK sends events directly to AWS API Gateway:

  • Events are sent to /v1/track or /v1/page endpoints
  • All URLs are hardcoded in the SDK
  • No write keys or configuration needed
  • Personalization requests go to AWS Decision API Gateway

Development

# Build
npm run build

# Watch mode
npm run dev

# Lint
npm run lint

Publishing (maintainers)

CI publishes via npm Trusted Publishing (GitHub ↔ npm, no long-lived token).

One-time setup on npm:

  1. If the package has never been published: Publish once with a token so the package exists: add NPM_TOKEN (Automation token) in repo Secrets, run the workflow, then remove the token and continue below.
  2. On npmjs.com: sign in → Packages@amplifyup/sdkSettingsTrusted publishing.
  3. Under “Select your publisher” choose GitHub Actions and set:
    • Workflow filename: publish-sdk.yml (must match exactly)
    • Repository/owner as prompted.
  4. Save. Future runs publish with no NPM_TOKEN secret.

Requires Node 22.14+ and npm 11.5.1+ (workflow uses Node 22).

License

MIT