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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@mutant-ws/next

v1.9.0

Published

Official browser tracking library for the Mutant Workspace.

Downloads

5

Readme

next

Official browser tracking library for the Mutant Workspace.

Install

npm install @mutant-ws/next

Use

set

Attach data to track calls. Find the productId from your profile page, in the install section of your product.

import { set } from "@mutant-ws/next"

set({
  productId: "UUID",
})

You can run set multiple times.

Ex. Attach userId to track calls after a successful login.

import { set } from "@mutant-ws/next"

const login = ({ email, password }) =>
  POST("/login", { body: { email, password } }).then(({ id }) => {
    set({
      userId: id,
    })
  })

track

Record an event your application.

  • name is required - Name of the event that you'll use to plot inside Mutant. An error will be thrown if not passed.
  • productId - You can either set productId once via set or explicitly add it to the track call.

If using BEM for naming events, when plotting an event, the legend label will only show the M (modifier) part of BEM. Ex. for page__section--login, only login will be displayed.

import { track } from "@mutant-ws/next"

track("page.section.action-name", {
  context: "data such as",
  userId: "can be added to",
  events: "by adding it here",
})

API

Make a POST at https://api.mutant.love/track with the same requirements as the track method (name and productId required).

Ex. Tracking CI deployment success and failure.

curl \
  --header "Content-Type: application/json" \
  --data '{"name": "ci.success", "productId": "uuid"}' \
  https://api.mutant.love/track

Cookies

  • mutant - Unique client id. Created if not present.

Collected data

We automatically collect the following data with every event.

  • Screen size: width and height of viewport and screen
  • User agent
  • URL
  • Referrer
  • IP
  • Timestamp

Develop

git clone [email protected]:mutant-ws/next.git && \
  cd next && \
  npm run setup

# run tests (any `*.test.js`) once
npm test

# watch `src` folder for changes and run test automatically
npm run tdd

Changelog

See the releases section for details.