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

@cloudcare/mobile-react-native-navigation

v0.4.3

Published

Automatic Guance RUM View tracking for react-native-navigation.

Readme

Guance React Native Navigation plugin

This plugin tracks Wix react-native-navigation screen appearances as Guance RUM Views and measures appearance loading.

Installation

yarn add @cloudcare/react-native-mobile @cloudcare/mobile-react-native-navigation

Keep your existing react-native-navigation dependency and its native setup. This plugin contains only JavaScript and types; it adds no native linking or build configuration.

View tracking

Initialize the mobile SDK and RUM, then start tracking before displaying the navigation root:

import { Navigation } from 'react-native-navigation';
import { FTRumReactNativeNavigationTracking } from '@cloudcare/mobile-react-native-navigation';

FTRumReactNativeNavigationTracking.startTracking();

Navigation.events().registerAppLaunchedListener(() => {
  // Register your screens, then display the root as usual.
  void Navigation.setRoot({
    root: { stack: { children: [{ component: { name: 'Home' } }] } },
  });
});

// Before shutting down the SDK or disposing the navigation integration:
FTRumReactNativeNavigationTracking.stopTracking();

startTracking() is idempotent. stopTracking() removes all registered global screen listeners and the AppState subscription. You can start tracking again; callbacks queued by an old registration cannot restart or stop the new registration's View. Starting after a screen is already visible only tracks subsequent appearance events, so start before setRoot.

The plugin listens directly to componentDidAppear and componentDidDisappear, and to componentWillAppear when the navigation library exposes it. It works without patching React.createElement and also covers screens using the automatic JSX runtime. Only events with componentType: 'Component' are treated as screens. Top bar titles, backgrounds, and buttons are excluded. componentName becomes the View name and componentId identifies the screen instance.

Loading and lifecycle

Loading is the monotonic elapsed time from componentWillAppear to componentDidAppear, reported in nanoseconds: 25.5 ms is 25,500,000 ns. This is the observed appearance interval, not the completion of asynchronous content loading. If the navigation library has no will-appear API, Views are collected without loading data. Missing starts and non-positive durations also omit loading data. Duplicate callbacks do not submit loading twice. Native closes automatic Views in the background; foreground recovery starts the current screen without replaying old loading data. A late disappearance from the previous screen cannot close a different active screen.

Use one automatic navigation integration at a time. The SDK has one active View; when multiple screens are simultaneously visible, the latest accepted appearance owns it. This package does not need React Navigation or @cloudcare/mobile-react-navigation.

Migration

Replace the copied example/src/FTRumReactNativeNavigationTracking.tsx import with @cloudcare/mobile-react-native-navigation, retaining the class name and methods. Remove the copied implementation so it cannot collect Views twice.

License

Apache 2.0