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

okxai-test-node-bindings

v1.12.0-alpha.1

Published

> [!INFO] > These bindings are not intended to be used directly, use the associated SDK instead.

Readme

Node bindings for the libXMTP rust library

[!INFO] These bindings are not intended to be used directly, use the associated SDK instead.

Code Organization

The Rust source code follows a modular structure organized by domain:

src/
├── lib.rs                 # Library entry point, ErrorWrapper utility
├── client/                # Client struct and methods (split by concern)
├── conversations/         # Conversations methods (list, create, stream)
├── conversation/          # Conversation methods (split by concern)
├── content_types/         # Content type definitions (one file per type)
│   ├── mod.rs             # ContentType enum and re-exports
│   ├── text.rs, reaction.rs, reply.rs, attachment.rs, ...
├── messages/              # Message types and utilities
│
└── [root-level files]   # Shared types, enums, and utils used across modules

Where to Find Code

  • Client methods: src/client/ - Find the file matching the concern (signatures, consent, etc.)
  • Creating clients: src/client/create_client.rs and src/client/options.rs
  • Listing/creating conversations: src/conversations/
  • Single conversation operations: src/conversation/
  • Group-specific operations: src/conversation/group/
  • Dm-specific operations: src/conversation/dm.rs
  • Content type definitions: src/content_types/
  • Message types: src/messages/
  • Shared types/enums: Root-level files in src/

Where to Add New Code

  • New Client method: Add to existing file in src/client/ by concern, or create new file if new concern
  • New Conversations method: Add to src/conversations/mod.rs or appropriate submodule
  • New Conversation method: Add to src/conversation/mod.rs or appropriate submodule
  • New content type: Create src/content_types/<type_name>.rs and add to mod.rs
  • New shared type/enum: Create root-level file in src/

Useful commands

  • yarn: Installs all dependencies (required before building)
  • yarn build: Build a release version of the Node bindings for the current platform
  • yarn lint: Run cargo clippy and fmt checks
  • yarn test: Run the test suite on Node

Testing

Before running the test suite, a local XMTP node must be running. This can be achieved by running ./dev/up at the root of this repository. Docker and Rust are required.