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

@ariada-org/core-browser

v0.1.1

Published

In-browser DOM adapter for @ariada-org/core-engine — used by the ariada Chrome extension to scan the live document without Node or Playwright.

Readme

@ariada-org/core-browser

In-browser DOM adapter for @ariada-org/core-engine. Powers the ariada Chrome extension and any other browser-context consumer that needs to run a scan without Node, Playwright, or pino in the bundle.

| Field | Value | | -------------- | ---------------------------------------------------------------- | | Package name | @ariada-org/core-browser | | Version | 0.1.0 | | Licence | EUPL-1.2 (European Union Public Licence) | | Runtime | Browser only (ES2022, no Node API surface) | | Dependencies | @ariada-org/core-engine (workspace) | | Bundle size | ≤ 50 KB minified (esbuild target, verified via bundle:size) | | REUSE-compliant | yes — REUSE.toml + per-file SPDX headers |

Public API (v0.1)

import {
  captureBrowserSnapshot,
  scanCurrentDocument,
  createDomBoundingBoxResolver,
} from '@ariada-org/core-browser';
  • captureBrowserSnapshot(opts) — read a UnifiedSnapshot from a live Document. Optionally pulls the full AX tree via a chrome.debugger shim (extension context only).
  • scanCurrentDocument(opts?) — run the engine orchestration end-to-end against the current document. Drop-in equivalent of @ariada-org/core-playwright's scan() but for browser context. Returns a Promise<UnifiedReport>.
  • createDomBoundingBoxResolver(document) — element-iter resolver that wraps Element.getBoundingClientRect.

Usage — Chrome extension content script

// content-script.ts
import { scanCurrentDocument } from '@ariada-org/core-browser';

chrome.runtime.onMessage.addListener(async (msg, _sender, send) => {
  if (msg.type !== 'ARIADA_SCAN_REQUEST') return;
  // `scanCurrentDocument` returns a `ScanResult` (engine type) — pull
  // `.report` for the `UnifiedReport`. Pass `analyzers` (engine
  // `DomainAnalyzer[]`); the package adds no domain-name shorthand on top.
  const result = await scanCurrentDocument({ document, analyzers: [] });
  send({ type: 'ARIADA_SCAN_RESULT', report: result.report });
  return true; // async
});

Usage — generic in-browser embed

import {
  captureBrowserSnapshot,
  scanCurrentDocument,
} from '@ariada-org/core-browser';

// Snapshot-only capture (no engine orchestration). `scanId` is required.
const snapshot = await captureBrowserSnapshot({ document, scanId: 'my-scan' });

// Or full scan end-to-end. Returns a `ScanResult`; `.report` is the
// `UnifiedReport`. Pass engine `DomainAnalyzer[]` as `analyzers` (this
// package adds no domain-name shorthand on top of the engine API).
const { report } = await scanCurrentDocument({ document, analyzers: [] });

Bundle-size discipline

The package ships only ES2022 modules; the public bundle target is ≤ 50 KB minified, verified via pnpm --filter @ariada-org/core-browser bundle:size and recorded in the engine-split BUILD_REPORT. The size budget is enforced because the Chrome extension content-script must stay under the MV3 (Manifest V3) inline-script size limit for fast injection. Avoid pulling Node-only modules — there is no polyfill layer.

Testing

Unit tests run with vitest + happy-dom:

pnpm --filter @ariada-org/core-browser test

Layout

src/
  index.ts            — public exports
  browser-runner.ts   — scanCurrentDocument()
  dom-snapshot.ts     — captureBrowserSnapshot()
  bbox-resolver.ts    — createDomBoundingBoxResolver()
tests/
  *.test.ts           — vitest + happy-dom

Licence

EUPL-1.2 — see LICENSE. Per-file SPDX headers + REUSE.toml keep machine-readable metadata in sync. Trademarks not granted; see TRADEMARK.md.

Security

Vulnerability reports → https://github.com/ariada-org/ariada/security/advisories/new or [email protected]. See SECURITY.md.