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

@vyro-x/sentry

v0.1.0

Published

Vyro's shared Sentry setup: environment-specific init wrappers with built-in secret scrubbing (authorization headers, API keys, tokens).

Downloads

256

Readme

@vyro-x/sentry

Vyro's shared Sentry setup. One package that owns the Sentry version and gives every service and frontend a ready-to-use initSentry(...) with secret scrubbing already wired in — so Authorization headers, API keys, tokens and other secrets never reach Sentry.

Why

Previously every project called Sentry.init(...) itself, on a different SDK version (@sentry/node alone spanned five v7 ranges plus v8), each re-implementing config and scrubbing. This package centralises all of it:

  • One pinned Sentry version, declared here as a peer dependency.
  • Scrubbing on by default — no way to forget it.
  • Per-environment entry points, because backends, SPAs and Next.js each need a different SDK and config.

Entry points

| Import | SDK (peer) | Use in | | --- | --- | --- | | @vyro-x/sentry | none | shared scrubbing / config helpers | | @vyro-x/sentry/node | @sentry/node | Express / Lambda services | | @vyro-x/sentry/browser | @sentry/react | Vite + React SPAs | | @vyro-x/sentry/nextjs | @sentry/nextjs | modern-website |

The SDK peers are optional — installing @vyro-x/sentry in a backend pulls only @sentry/node.

Usage

Backend (@sentry/node)

// src/shared/sentry.ts (or inline)
import { initSentry } from "@vyro-x/sentry/node"

initSentry({ serverName: "users-api" }) // DSN read from process.env.SENTRY_DSN

export { captureException, setupExpressErrorHandler } from "@vyro-x/sentry/node"

Sentry.Handlers.requestHandler() is gone in v8+. If a service needs Express error reporting, call setupExpressErrorHandler(app) after your routes.

Frontend SPA (@sentry/react)

import { initSentry, ErrorBoundary } from "@vyro-x/sentry/browser"

initSentry({ dsn: import.meta.env.VITE_SENTRY_DSN, tracesSampleRate: 0.2 })

Next.js (@sentry/nextjs)

// sentry.server.config.ts / sentry.client.config.ts / sentry.edge.config.ts
import { initSentry } from "@vyro-x/sentry/nextjs"

initSentry({ serverName: "modern-website-frontend" })

What gets scrubbed

request.headers, request.cookies, request.data, contexts, extra, tags on every event, and breadcrumb data. Default keys (case-insensitive): authorization, api-key / apikey / api_key / x-api-key, x-hasura-admin-secret, access-token, refresh-token, token, secret, cookie, password, credential. Extend via the scrub option (extraKeys, extraPatterns, pattern, placeholder, maxDepth), or use the low-level scrubSentrySensitiveData from the root entry.

Test

pnpm --filter @vyro-x/sentry test