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

@plyven/react-native

v0.1.1

Published

React Native bridge for Plyven using native Android/iOS SDKs

Readme

@plyven/react-native

React Native bridge that configures the existing Plyven native SDKs:

| Platform | Native SDK | How RN wires it | |----------|------------|-----------------| | Android | com.plyven:api-inspector-sdk (OkHttp) | RN OkHttpClientProvider factory + optional applyTo(builder) | | iOS | ios/ SwiftPM Plyven (URLProtocol) | Plyven.install(DebugConfig…) via native module |

  • Debug / __DEV__ only
  • No cloud / telemetry

Full guide: React Native install

SDK distribution status: SDK release notes

Install (0.1.0)

Not published to the npm registry yet. Until a release explicitly publishes @plyven/react-native, install from this repository (path or staged tarball). The plyven-rn.podspec is for local / autolink installs only — not CocoaPods trunk.

Local / path (supported today)

npm install ../path/to/Plyven/packages/react-native

Staged tarball (supported today)

After scripts/stage-sdk-release.ps1 in the Plyven repo:

npm install ../path/to/Plyven/dist/sdk/plyven-react-native-0.1.0.tgz

Public npm (future only)

When this package is actually published:

npm install @plyven/react-native

Do not use the registry command above until publish succeeds (npm view @plyven/react-native must resolve).

Why this package ships TypeScript source

This package intentionally distributes TypeScript source (main / react-native → src/index.ts) plus native Android/iOS bridge files. React Native’s Metro bundler compiles that source in the app. There is no separate JS dist/ build step for the JS bridge — that is intentional, not an incomplete publish layout.

Consumers need:

  • A normal React Native app (Metro / autolinking)
  • Android: Maven Local (or a future public Maven artifact) for com.plyven:api-inspector-sdk
  • iOS: local SwiftPM package from the Plyven repo’s ios/ directory (not a GitHub SPM URL for this monorepo yet)

JS

import { Plyven } from "@plyven/react-native";

if (__DEV__) {
  Plyven.install({
    host: process.env.PLYVEN_HOST ?? "192.168.1.10", // device → PC LAN IP
    port: 8081,
  });
}

Android

  1. Publish the Android SDK to Maven Local from the Plyven repo:
    cd android && ./gradlew :inspector-okhttp:publishToMavenLocal
  2. Ensure mavenLocal() is in repositories and depend on com.plyven:api-inspector-sdk:0.1.0 (debug).
  3. Autolink registers PlyvenPackage (or add packages.add(new com.plyven.rn.PlyvenPackage());).
  4. Call Plyven.install({ host, port }) from JS in __DEV__.

Custom OkHttp clients can call PlyvenNative.applyTo(builder) from Kotlin.

iOS

  1. Add the Plyven Swift package (ios/ in the Plyven repo) to the Xcode workspace / app target (DEBUG).
  2. Autolink / pod install for plyven-rn.
  3. Call Plyven.install({ host, port }) from JS in __DEV__.

License

Proprietary — Plyven Commercial Software and SDK License. license in package.json is UNLICENSED. Not open source.