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 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-native-stack-tracer

v0.2.1

Published

React Native Android StackTracer

Downloads

6

Readme

ReactNative-StackTracer Release

Support for React Native stack traces on Crashylitics and other crash report tools for Android.

Motivation

When a fatal Javascript error happens in production for your React Native App, the ExceptionsManagerModule wraps the Javascript stack trace in the message field of a JavaScriptException and throws it. That is good because the fatal JS error can be captured by crash report tools such as Crashlytics. On the other hand it is bad because the JavascriptException is always thrown in the same place. Therefore all JS crashes look the same because they have the exact same Java stack trace :

Crashlytics stack trace

Would not be wonderful if instead of having the same Java stacktrace over and over again we could have the JavaScript stack? So distinct JS crashes would yield distinct entries on Crashlytics? Your wish just became true with this little library!

Crashlytics stack trace

##Yet another Crashlytics React-Native module? No. This library doesn't deal with logs like it is done here nor it exposes the Crashlytics API to Javascript like this project.

This library sinthesizes a Java stack that is similar to the JS one. The advantages of this technique is that distinct JS crashes will have have distinct entries on the Crashlytics Dashboard, making fatal JS errors easy to track as the native crashes.

##What about iOS? This library doesn't support iOS. The fact that Android is not actually native (Android apps run on top of a Java virtual machine, Dalvik or Art), makes it easy to fake program stacks. iOS is really native, so its programing stack is a real one controled by the device's processor.

##How to use it

Step 1 - Add the library to the Android project, the android folder inside your React Native project.

  • Add it in your root build.gradle at the end of repositories:
	allprojects {
		repositories {
			...
			maven { url "https://jitpack.io" }
		}
	}
  • Add the dependency
	dependencies {
		compile "com.github.aoriani:ReactNative-StackTracer:0.1.1"
	}

Step 2 - Add StrackTracePackage to your ReactNativeHost:

import com.github.aoriani.rnstacktracer.StackTracePackage;

...

private final ReactNativeHost mReactNativeHost = new ReactNativeHost(this) {
        @Override
        protected boolean getUseDeveloperSupport() {
            return BuildConfig.DEBUG;
        }

        @Override
        protected List<ReactPackage> getPackages() {
            List<ReactPackage> packages = new ArrayList<>();
            packages.add(new MainReactPackage());
            if (!BuildConfig.DEBUG) {
                packages.add(new StackTracePackage());
            }
            return packages;
        }
    };

Warning: It's advisable to only add the StackTracePackage in production. You still want to see the "Red Screen of Death" during development.