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

@device-router/probe

v1.0.1

Published

Lightweight (~1 KB gzipped) client-side probe for collecting device capability signals

Readme

@device-router/probe

A ~1 KB (gzipped) client-side probe that collects device capability signals via browser APIs for DeviceRouter.

Installation

pnpm add @device-router/probe

How it works

The probe runs once per session in the browser. It collects device signals using standard browser APIs, then POSTs them to your server's probe endpoint. A session cookie prevents repeated collection.

Browser                                      Server
  │                                            │
  │  collectSignals()                          │
  │  getBattery()                              │
  │                                            │
  │  POST /device-router/probe                 │
  │  ─────────────────────────────────────>    │
  │  { hardwareConcurrency: 8,                 │
  │    deviceMemory: 8, ... }                  │
  │                                            │
  │  { sessionToken: "abc123" }                │
  │  <─────────────────────────────────────    │
  │                                            │
  │  Set cookie: device-router-session=abc123  │
  └────────────────────────────────────────────┘

Usage

Script tag (IIFE)

The simplest approach — include the pre-built bundle:

<script src="/device-router-probe.min.js"></script>

The probe auto-executes on load. Serve the file from dist/device-router-probe.min.js.

Auto-injection

Middleware packages can auto-inject the probe into HTML responses:

const { middleware, probeEndpoint, injectionMiddleware } = createDeviceRouter({
  storage,
  injectProbe: true,
});

Programmatic

import { runProbe } from '@device-router/probe';

await runProbe({
  endpoint: '/device-router/probe', // default
  cookieName: 'device-router-session', // default
  cookiePath: '/', // default
});

Programmatic with retry

import { runProbeWithRetry } from '@device-router/probe';

await runProbeWithRetry({
  endpoint: '/device-router/probe',
  retry: {
    maxRetries: 3, // default: 3
    baseDelay: 500, // default: 500ms
    maxDelay: 5000, // default: 5000ms
  },
});

Uses exponential backoff with jitter on network failure. Signals are collected once before the retry loop. Does not affect the IIFE bundle size.

Signals collected

| Signal | API | Browser Support | | ---------------------- | -------------------------- | ------------------- | | CPU cores | hardwareConcurrency | All modern browsers | | Device memory | deviceMemory | Chromium | | Connection info | navigator.connection | Chromium | | User agent | navigator.userAgent | All browsers | | Viewport dimensions | window.innerWidth/Height | All browsers | | Pixel ratio | devicePixelRatio | All browsers | | Prefers reduced motion | matchMedia | All modern browsers | | Color scheme | matchMedia | All modern browsers | | GPU renderer | WebGL debug info | Most browsers | | Battery status | navigator.getBattery() | Chromium |

All signals are optional — the probe gracefully degrades based on what the browser supports. Unavailable APIs are silently skipped.

Bundle size

The IIFE bundle is strictly capped at 1024 bytes gzipped. This is enforced at build time — the build fails if the limit is exceeded.

Exports

  • runProbe(options?) — Run the probe (async, idempotent per session)
  • collectSignals() — Collect all synchronous device signals
  • ProbeSignals — Type for the collected signal object
  • ProbeOptions — Configuration type for runProbe
  • runProbeWithRetry(options?) — Run the probe with retry on failure
  • RetryOptions — Retry configuration type
  • ProbeWithRetryOptions — Configuration type for runProbeWithRetry

Individual collectors are also exported for selective use:

  • collectHardwareConcurrency()
  • collectDeviceMemory()
  • collectConnection()
  • collectUserAgent()
  • collectViewport()
  • collectPixelRatio()
  • collectPrefersReducedMotion()
  • collectPrefersColorScheme()
  • collectGpuRenderer()

License

MIT