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

@nilguard/react

v0.1.2

Published

React bindings for the Nilguard browser SDK: provider, hook, and error boundary.

Readme

@nilguard/react

Thin React bindings over @nilguard/browser-sdk: a provider that owns the SDK lifecycle, a hook to reach the client, and an error boundary that reports render-phase crashes (which React otherwise swallows).

npm install @nilguard/react @nilguard/browser-sdk

react and react-dom (>=18) are peer dependencies.

Usage

Wrap your app once. The provider initializes the SDK on mount and keeps the metadata in sync — pass changing userHash/featureFlags/etc. and they are applied via setMetadata without re-initializing.

import { NilguardProvider, NilguardErrorBoundary } from "@nilguard/react";

function Root({ user }: { user?: string }) {
	return (
		<NilguardProvider
			options={{
				siteToken: import.meta.env.VITE_NILGUARD_SITE_TOKEN,
				appId: "my-app",
				environment: "production",
				release: __GIT_SHA__,
				userHash: user,
				replay: { mode: "buffered" },
				console: { mode: "warn-and-error" },
				network: { mode: "metadata" },
				sessionEnd: { mode: "full" },
			}}
		>
			<NilguardErrorBoundary fallback={(err) => <Crashed error={err} />}>
				<App />
			</NilguardErrorBoundary>
		</NilguardProvider>
	);
}

Unhandled window.error / unhandledrejection are captured automatically by the browser SDK. The error boundary covers the gap React leaves: it reports render-phase errors through the client (or re-throws to the global listener if no provider is mounted).

Manual capture

import { useNilguard } from "@nilguard/react";

function PayButton() {
	const nilguard = useNilguard();
	return (
		<button
			onClick={() => {
				try {
					pay();
				} catch (err) {
					nilguard?.reportError(err, { flow: "checkout" });
				}
			}}
		>
			Pay
		</button>
	);
}

useNilguard() returns the NilguardClient (reportError, markCrash, setMetadata, stop) or null before init / outside a provider.

API

  • NilguardProvider({ options, children })options is the browser SDK's NilguardOptions.
  • useNilguard(): NilguardClient | null
  • NilguardErrorBoundary({ children, fallback?, onError? })fallback may be a node or (error) => node.
  • init and all browser-SDK types are re-exported for convenience.