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

@parlox/browser

v1.0.3

Published

Parlox agent analytics for storefronts: see which AI agents visit, what they read, where they get stuck and whether they buy.

Readme

@parlox/browser

Parlox agent analytics for storefronts: which AI agents visit, what they read, where they get stuck and whether they buy. This package is the browser part; @parlox/server is the server part.

npm install @parlox/browser

React and Next.js

Render once, in the root layout (App Router or Pages Router). It renders nothing and starts after hydration.

import { ParloxAnalytics } from "@parlox/browser/react";

<ParloxAnalytics publicKey="pk_..." />

Anything else

import { init, track } from "@parlox/browser";

init({ publicKey: "pk_..." });
track("add_to_cart", { item_id: "sku-1", value: 49.9, currency: "USD", items: 1 });

| Option | Default | | |---|---|---| | publicKey | required | The site's public key from the Parlox dashboard. Safe in the browser. | | consent | "granted" | "required": nothing runs, is stored or is sent until consent(true). | | recordAgents | true | Record agent visits as a masked DOM replay. People are never recorded. |

track(name, props) takes GA4 ecommerce names (view_item, add_to_cart, remove_from_cart, view_cart, begin_checkout, add_shipping_info, add_payment_info, purchase, search) and only item_id, value (major units), currency, items, order_id, step. consent(granted) grants or withdraws. sessionId() returns the visit id to send with a checkout, so your server can post the confirmed order with @parlox/server.

What it does on your page, and what it never does

  • Counts page views and a summary of how the page was used (pointer movement, scrolling, clicks, time), and records what was clicked: a control's label (emails, phone numbers and digit runs masked), tag, id, classes, link path.
  • Reads your GA4 dataLayer and your store's cart API responses (Shopify /cart/add.js, WooCommerce) for commerce events. Wrapped functions (fetch, XMLHttpRequest.open, dataLayer.push, history.pushState) keep their behaviour and return values.
  • Never sets cookies. Never reads what visitors type (field names only). Strips capability tokens (checkout, order, reset links) from URLs and reduces the referrer to its origin.
  • Every listener and hook is wrapped: it cannot throw into your page. Safe to import during server-side rendering.
  • For automated browsers only, it loads the recorder (a separate chunk your bundler builds; a person's browser never loads it). Recordings mask every input and all text except button and link labels. Mark areas with data-plx-unmask (text may appear), data-plx-mask (mask a label too) or data-plx-block (leave out entirely).
  • Sends data only to https://gateway.parlox.io. With a Content-Security-Policy, allow it in connect-src.

No build step? Use the pinned script tag from the Parlox dashboard instead: the same code, served as an immutable release with an integrity hash.

Install guide: https://gateway.parlox.io/install.md