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

@centralchat/react-native-widget

v0.2.5

Published

The Central chat in a React Native app — three calls and one component, over the same page the web embed loads.

Readme

Central Chat — React Native

npm install @centralchat/react-native-widget react-native-webview
// App.tsx — mount the host ONCE, above your navigator, never inside a screen.
<><YourNavigator /><CentralChatHost /></>

CentralChat.init(entry)   // at start — warms everything
CentralChat.show()        // from your support button
CentralChat.hide()        // optional; the screen closes itself

entry is a channel key (businessId|chatAccountId, anonymous) or a mint user key your backend signed (that person). One argument, either door.

No native module — no pods, no autolinking, and it runs in Expo Go (except the camera; see below). RN 0.72+ · iOS 15 · minSdk 24.

Optional

CentralChat.onReady = () => {};                 // warm; enable your button here
CentralChat.onError = ({code, message}) => {};  // ENTRY_INVALID | TOKEN_EXPIRED | NETWORK | INTERNAL
CentralChat.useSecureStore({get, set, remove, list});  // before init — keeps the session out of WebView storage

Permissions, only for what your chat account offers: RECORD_AUDIO + MODIFY_AUDIO_SETTINGS and ACCESS_*_LOCATION on Android, the four NS*UsageDescription keys on iOS.

The camera needs one line of manifest, or it silently does nothing. Android 11+ shows an app only the apps it declares an interest in, and react-native-webview resolves the camera before launching it — so without this it finds nothing, gives up, and the button does not even flicker:

<queries>
  <intent><action android:name="android.media.action.IMAGE_CAPTURE"/></intent>
  <intent><action android:name="android.media.action.VIDEO_CAPTURE"/></intent>
</queries>

On Expo that is a config plugin — copy withCameraQueries.js. Do not declare CAMERA: the capture intent needs no permission, and declaring it makes both Android and react-native-webview start demanding one. Expo Go declares it, which is why the camera behaves differently there than in your own build — test this in a dev build, never in Expo Go.

Don't wrap the host in KeyboardAvoidingView — the page insets its own composer. Example: ../../example/react-native.