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

@focale/sdk

v0.1.0

Published

Focale OpenTelemetry SDK core (DSN, watch, redaction, OTLP JSON)

Readme

@focale/sdk

Shared Focale OpenTelemetry core: DSN parse, watch(), redaction, and OTLP/HTTP JSON exporters. Runtime start() lives in a separate package so land can add only the detected runtime.

import { start } from '@focale/sdk-node';
import { watch } from '@focale/sdk';

await start(); // FOCALE_DSN

export const POST = watch('auth.signup', async (req) => { /* existing */ });

| Package | Role | |---------|------| | @focale/sdk | core (watch, parseDsn, startProviders) | | @focale/sdk-node | Node start() + HTTP framework instrumentations | | @focale/sdk-browser | browser start() stub | | @focale/sdk-deno | Deno start() stub | | @focale/sdk-edge | edge start() stub |

Publishing

Releases go out from .github/workflows/sdk.yml on main via npm trusted publishing (OIDC). There is no NPM_TOKEN.

npm trust needs npm 11.15+ (Node 22 still ships npm 10). After each name exists on the registry, register the workflow while logged in as an @focale owner with 2FA:

npx -y npm@latest trust github @focale/sdk --repo focale/root --file sdk.yml --allow-publish

Repeat for @focale/sdk-node, @focale/sdk-browser, @focale/sdk-deno, and @focale/sdk-edge. Website equivalent: package Settings / access, organization focale, repository root, workflow filename sdk.yml, allowed action npm publish, no GitHub environment.

npm trust cannot create the first version: the package must already exist. Publish 0.1.0 once interactively from each package directory (2FA, no provenance), then run npm trust. pnpm --filter … pack fails on pnpm 9; pack from the package dir instead:

cd packages/sdk
tarball="$(pnpm pack --pack-destination /tmp | tail -n1)"
npm publish "$tarball" --access public

Repeat for sdk-node, sdk-browser, sdk-deno, sdk-edge. Later versions come from CI. After that you can require 2FA and disallow tokens.