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

@amboras-dev/omnisend

v1.0.1

Published

Omnisend browser events + slot components for Amboras storefronts

Readme

@amboras-dev/omnisend

Omnisend browser events + slot components for Amboras storefronts.

This package follows the slot-based (Class A) plugin convention: its components are bound to named storefront plugin slots via the catalog manifest and compiled into the storefront's generated registry. It mirrors @amboras-dev/pinterest.

Exports

| Entry | Purpose | Runtime | | --- | --- | --- | | . | Public types + getOmnisendConfig + low-level track / identifyContact accessors | server-safe | | ./slot-components | OmnisendProvider, OmnisendViewItem, OmnisendAddToCart | client ("use client") | | ./get-config | getOmnisendConfig() on its own | server-safe |

Slot components

OmnisendProviderrootProviders slot

Props (via propsFromConfig): { brandID?: string }.

  • Renders null when no brandID (Omnisend disabled).

  • Injects the bootstrap snippet once via an inline next/script (id="omnisend-bootstrap"), consent-gated on amboras_consent and re-checked on amboras-consent-changed:

    window.omnisend = window.omnisend || [];
    omnisend.push(["brandID","<brandID>"]);
    omnisend.push(["track","$pageViewed"]);
    !function(){var e=document.createElement("script");e.type="text/javascript",e.async=!0,e.src="https://omnisnippet1.com/inshop/launcher-v2.js";var t=document.getElementsByTagName("script")[0];t.parentNode.insertBefore(e,t)}();
  • Fetches the authenticated customer (on mount + amboras-auth-changed) and calls identifyContact({ email, phone }). Omnisend rejects events from anonymous visitors, so the identify is what makes the other slots' events land.

OmnisendViewItempdpAnalytics slot

Props (via propsFromContext): { productId?, productName?, sku?, price?, currency?, imageUrl?, url?, categories? }.

Fires viewed product (eventVersion:"v4", origin:"api") once per productId. Money: price is passed through unchanged — Medusa minor units (cents) == Omnisend viewed-product cents.

OmnisendAddToCartcartUpdate slot

Props (via propsFromContext): { cartId?, itemCount?, total?, currency? }.

Fires added product to cart (origin:"api", eventVersion:"") when the cart signature changes. Money: value = toMajorUnits(total, currency) (decimal major units) — unlike the viewed-product event. The cart slot only exposes cart-level context, so the event carries cart value, not per-product detail.

Config

getOmnisendConfig() reads the generic /store/integrations/active route (with x-publishable-api-key + optional X-Store-Environment-ID) and returns { enabled, brandID } | null from the response's omnisend key. Fail-closed null on any error. The Omnisend secret API key never leaves the Medusa side.