6cc24d2cbd | ||
---|---|---|
examples/Snoopful | ||
media | ||
stream | ||
.eslintrc.js | ||
.gitignore | ||
.npmignore | ||
README.md | ||
formatting.js | ||
index.js | ||
log.js | ||
package.json |
README.md
React Native Snoopy
UPDATE: I wrote an article with the story behind this library.
Snoopy is a profiling tool for React Native, that lets you snoop on the React Native Bridge using the MessageQueue spy feature.
With Snoopy you can tame a stream of events, using Rx and a few built-in goodies, to locate performance hogs, problems, and expose unexpected communications on the bridge.
The React Native bridge is the hub where communication between the Javascript and the Native world happen. Optimizing and catching unexpected (bad) communications can make or break your performance. Being that central and sensitive place, it made sense to have tooling built around it.
NOTE: Snoopy is a developer tool, and you might want to flag it under __DEV__
. I felt
not doing this by default inside Snoopy will allow for creative uses even in production.
Quick Start
$ npm install -S rn-snoopy
First, find a place to initialize Snoopy and the event stream, doesn't matter where, but
preferably under an if(__DEV__)
guard.
// core Snoopy
import Snoopy from 'rn-snoopy'
// some Snoopy goodies we're going to use
import bars from 'rn-snoopy/stream/bars'
import filter from 'rn-snoopy/stream/filter'
import buffer from 'rn-snoopy/stream/buffer'
import EventEmitter from 'react-native/Libraries/vendor/emitter/EventEmitter';
const emitter = new EventEmitter()
const events = Snoopy.stream(emitter)
In the following examples, we're going to use info
, the call descriptor.
{
type: int (0=N->JS, 1=JS->N)
method: string,
module: string,
args: object,
}
Examples
Show only calls going from Javascript to Native create an info
shape with
Snoopy.TO_NATIVE
. Use true
to log filter results.
filter({ type: Snoopy.TO_NATIVE }, true)(events).subscribe()
Show calls to createView
. Filter based on method
, and provide a shape to match it.
filter({ method:'createView' }, true)(events).subscribe()
Drill down and show only calls with specific arguments, using nested matching.
filter({ method:'createView', {args: {foo: {bar:1}}}}, true)(events).subscribe()
Or use a function.
filter((info)=>info.method == 'createView', true)(events).subscribe()
Visualize "excessive" calls across the bridge. Group and aggregate calls per second.
bars()(
buffer()(
events
)
).subscribe()
Visualize "heavy" calls across the bridge. Use a heuristic: serialize arguments and take the size.
bars(info=>JSON.stringify(info.args).length)(
events
).subscribe()
Visualize "heavy" calls across the bridge. Set a threshold (100
) and pop a Yellowbox (true
) in Simulator
to warn about crossing the threshold.
bars(info=>JSON.stringify(info.args).length
200 /*command string length threshold*/,
true /*show yellow box*/
)(events).subscribe()
Visualize "heavy" calls, only for view creation. This filters on createView
and takes a look at the
argument data size.
bars(info=>JSON.stringify(info.args).length)(
filter({ method:'createView' })(events)
).subscribe()
React Native Below 0.33
I've submitted a modification to MessageQueue
that allows for more flexible bridge spy,
which was made available starting React Native v0.33. Versions 0.33 and up will work seamlessly with Snoopy.
For versions below 0.33, you have the option of locking to a legacy version of Snoopy which
installs the required MessageQueue
modifications by patching it externally:
$ npm i rn-snoopy@1.0.6
Contributing
Fork, implement, add tests, pull request, get my everlasting thanks and a respectable place here :).
Thanks:
To all Contributors - you make this happen, thanks!
Copyright
Copyright (c) 2016 Dotan Nahum @jondot. See LICENSE for further details.