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

@oluso/react-native

v1.1.0

Published

Oluso error monitoring for React Native applications: an error boundary, provider, and hook for automatic and manual error reporting

Readme

@oluso/react-native

AI-powered error monitoring for React Native applications: automatic error reporting, breadcrumb tracking, and intelligent error grouping on-device.

Installation

npm install @oluso/react-native

Optional, but recommended so queued reports survive app restarts:

npm install @react-native-async-storage/async-storage

Features

  • Error Boundary: Catches render-time errors in a subtree and reports them automatically.
  • Global Capture: Catches uncaught JS exceptions and fatal errors via ErrorUtils, without disabling React Native's own red-box/crash handling.
  • Breadcrumbs: Tracks events leading to an error for better debugging.
  • User Context: Tie errors to specific users.
  • Deduplication: Intelligent fingerprinting groups similar errors together.
  • Offline Reliability: Queues reports (in AsyncStorage, when installed) when the network is unreachable, and retries on the next successful send. Without AsyncStorage, the queue still works for the current app session, it just doesn't survive a restart.

Usage

Wrap your app in OlusoProvider, then use ErrorBoundary around any subtree you want to protect:

import { OlusoProvider, ErrorBoundary, useOluso } from '@oluso/react-native';
import { Text, View } from 'react-native';

export default function App() {
  return (
    <OlusoProvider options={{ apiKey: 'your-api-key', environment: 'production' }}>
      <Dashboard />
    </OlusoProvider>
  );
}

function Dashboard() {
  const oluso = useOluso();

  return (
    <ErrorBoundary client={oluso} fallback={<Text>Something went wrong.</Text>}>
      <Widgets />
    </ErrorBoundary>
  );
}

Note: like all React error boundaries, ErrorBoundary only catches errors thrown during rendering, in lifecycle methods, and in constructors — not in event handlers or async code. Those are still caught by the global ErrorUtils handler, or can be reported manually with useOluso().captureException().

Manual Reporting & Context

import { useOluso } from '@oluso/react-native';

function CheckoutButton() {
  const oluso = useOluso();

  const handlePress = async () => {
    oluso.addBreadcrumb({ message: 'User started checkout', category: 'action' });

    try {
      await checkout();
    } catch (error) {
      oluso.captureException(error as Error, { step: 'checkout' });
    }
  };

  return <Button title="Checkout" onPress={handlePress} />;
}

Advanced Configuration

new OlusoClient({
  apiKey: 'your-api-key',
  endpoint: 'https://api.oluso.dev/api/v1/error/report', // override for self-hosting
  environment: 'staging',
  defaultSeverity: 'medium',
  maxBreadcrumbs: 50,
  maxErrorsPerMinute: 100,
  enableOfflineQueue: true,
  sensitiveKeys: ['ssn', 'api_key'],
  shouldReport: (err) => !err.message.includes('Failed to fetch'),
});

Process monitors

The OlusoClient instance exposes heartbeat(url, options), assertOutcome(options), and workflow(reference, runId?), with the same redaction and retry guarantees as the other JavaScript SDKs. See the complete monitor guide.

License

MIT