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

@hackler/react-native-webview-plugin

v2.0.0

Published

Hackle WebView bridge for React Native

Downloads

159

Readme

@hackler/react-native-webview-plugin

npm version docs changelog license

Hackle WebView bridge plugin for React Native.

Requirements

  • react-native >= 0.74.0
  • react-native-webview >= 13.13.0
  • @hackler/react-native-sdk >= 4.0.0 < 5.0.0
  • iOS 13.0+, Android API 24+

Installation

npm install @hackler/react-native-webview-plugin
# or, using yarn:
# yarn add @hackler/react-native-webview-plugin

Quick Start

Wrap your <WebView> with <HackleWebViewBridge>. It must be exactly one direct <WebView> child.

import { WebView } from 'react-native-webview';
import { HackleWebViewBridge } from '@hackler/react-native-webview-plugin';

function MyWebView() {
  return (
    <HackleWebViewBridge>
      <WebView source={{ uri: 'https://your-website.com' }} />
    </HackleWebViewBridge>
  );
}

With Configuration Options

import { WebView } from 'react-native-webview';
import { HackleWebViewBridge } from '@hackler/react-native-webview-plugin';

function MyWebView() {
  return (
    <HackleWebViewBridge
      automaticScreenTracking
      automaticEngagementTracking
      automaticRouteTracking>
      <WebView
        source={{ uri: 'https://your-website.com' }}
        onMessage={handleMessage}
        ref={webViewRef}
      />
    </HackleWebViewBridge>
  );
}

Configuration Options

| Option | Type | Default | Description | | ----------------------------- | --------- | ------- | -------------------------------------------- | | automaticScreenTracking | boolean | false | Automatically collect $page_view events | | automaticEngagementTracking | boolean | false | Automatically collect engagement events | | automaticRouteTracking | boolean | true | Automatically collect page route information | | style | ViewStyle | { flex: 1 } | Applied to the container view that wraps your WebView |

Migrating from 1.x

createHackleWebViewConfig and the nativeConfig prop are gone.

// before (1.x)
const config = createHackleWebViewConfig({ automaticScreenTracking: true });
<WebView source={{ uri }} nativeConfig={config} />

// after (2.x)
<HackleWebViewBridge automaticScreenTracking>
  <WebView source={{ uri }} />
</HackleWebViewBridge>

Option names and defaults are unchanged. The container adds one view layer, so give it the layout style your WebView used to receive (or rely on the flex: 1 default).