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

@flinkk/sentry-config

v1.0.3

Published

Shared Sentry configuration objects for Flinkk's Next.js apps, so client/server/edge error tracking is configured identically everywhere instead of copy-pasted per app.

Downloads

344

Readme

@flinkk/sentry-config

Shared Sentry configuration objects for Flinkk's Next.js apps, so client/server/edge error tracking is configured identically everywhere instead of copy-pasted per app.

Exports

| Subpath | What it is | | --- | --- | | @flinkk/sentry-config | Re-exports everything below from one entry point. | | @flinkk/sentry-config/client | sentryClientConfig — browser-side Sentry.BrowserOptions. | | @flinkk/sentry-config/server | sentryServerConfig — Node-side Sentry.NodeOptions, includes nodeProfilingIntegration. | | @flinkk/sentry-config/edge | sentryEdgeConfig — edge-runtime-safe options (no Node-only integrations). | | @flinkk/sentry-config/user-context | setSentryUserContext(user) — attaches the current user/tenant to the active Sentry scope. |

Sampling is driven by NEXT_PUBLIC_ENVIRONMENT rather than NODE_ENV, since hosting platforms often set NODE_ENV=production for preview deployments too — this keeps preview environments on full sampling instead of being mistaken for real production traffic. PII scrubbing (before-send.ts) and trace-propagation targets are shared across all three runtimes.

Usage

// sentry.client.config.ts
import * as Sentry from "@sentry/nextjs";
import { sentryClientConfig } from "@flinkk/sentry-config/client";

Sentry.init(sentryClientConfig);
// sentry.server.config.ts
import * as Sentry from "@sentry/nextjs";
import { sentryServerConfig } from "@flinkk/sentry-config/server";

Sentry.init(sentryServerConfig);
import { setSentryUserContext } from "@flinkk/sentry-config/user-context";

setSentryUserContext({ id: session.userId, tenantId: session.tenantId });

Environment variables

  • NEXT_PUBLIC_SENTRY_DSN — required for any events to actually send.
  • NEXT_PUBLIC_ENVIRONMENT — determines sampling rate (full sampling unless this is exactly "production").

License

ISC License - Internal Flinkk library