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

@myatthirikhin/chat-expo

v0.1.0

Published

Expo media capture for @myatthirikhin/chat-react-native — photos, documents and voice messages.

Downloads

161

Readme

@myatthirikhin/chat-expo

Media capture for @myatthirikhin/chat-react-native: photos, documents and voice messages, built on Expo modules.

Optional. Skip it and the composer renders without attach or mic buttons — which is exactly what a bare React Native app with no media modules should get.

pnpm add @myatthirikhin/chat-expo
npx expo install expo-image-picker expo-document-picker expo-image-manipulator expo-audio

Use

import { createExpoFilePicker, useExpoAudioRecorder } from '@myatthirikhin/chat-expo';

const filePicker = createExpoFilePicker();

function App() {
  // A HOOK, unlike the picker — see below.
  const recorder = useExpoAudioRecorder();

  return (
    <ChatProvider client={chat} filePicker={filePicker} recorder={recorder}>
      <ChatScreen conversationId={id} myId={me} />
    </ChatProvider>
  );
}

Why one is a factory and the other is a hook

IAudioRecorder is an imperative interface precisely so implementations aren't forced to be hooks. This one has to be anyway: expo-audio exports AudioRecorder as a type only, and useAudioRecorder() is the only runtime way to obtain an instance.

A future recorder built on something else can be a plain factory without changing the port.

Why this is a separate package

peerDependenciesMeta.optional is a package-manager contract that Metro does not read. An unresolvable static import is a hard bundling failure, not a runtime undefined, and even a try/catch require emits resolution warnings. Splitting the Expo-dependent code into its own package is the only way to make attachments genuinely optional.

It also matters for adoption: installing expo in a bare React Native CLI app requires npx install-expo-modules and an iOS deployment target of 16.4. That's a real cost, and no consumer should pay it just to render text messages.

Bare React Native CLI

These are ordinary Expo modules, so they work outside Expo — you just have to install the runtime first:

npx install-expo-modules@latest

See Expo's guide. Note the iOS 16.4 floor.

Peers

expo-image-picker · expo-document-picker · expo-image-manipulator · expo-audio · react

Deliberately loose version ranges (*): Expo module versions are pinned to the consumer's SDK, and a narrow range here would block every SDK upgrade.

License

MIT