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

@assistant-ui/metro

v0.0.15

Published

Metro / Expo integration for assistant-ui: the "use generative" directive compiler that colocates a tool's schema, server execute, and client render in one file. Works with Expo and bare React Native.

Readme

@assistant-ui/metro

Metro / Expo integration for assistant-ui: the "use generative" directive compiler for React Native. It lets you author tools with the same defineToolkit API as on the web: one file colocating a tool's schema, its execute, and its render, then compiles them for the device (and any Expo Router server route).

Works with Expo and bare React Native (both bundle with Metro).

Install

npm install --save-dev @assistant-ui/metro

Setup

Wrap your Metro config with withAui:

// metro.config.js
const { getDefaultConfig } = require("expo/metro-config");
const { withAui } = require("@assistant-ui/metro");

const config = getDefaultConfig(__dirname);

module.exports = withAui(config);

Bare React Native (without Expo):

// metro.config.js
const { getDefaultConfig } = require("@react-native/metro-config");
const { withAui } = require("@assistant-ui/metro");

module.exports = withAui(getDefaultConfig(__dirname));

Usage

Author a "use generative" toolkit exactly like on the web, importing defineToolkit from @assistant-ui/react-native:

// toolkit.tsx
"use generative";

import { defineToolkit } from "@assistant-ui/react-native";
import { z } from "zod";
import { WeatherCard } from "./WeatherCard";

export default defineToolkit({
  get_weather: {
    description: "Get the weather for a city.",
    parameters: z.object({ city: z.string() }),
    execute: async ({ city }) => {
      "use client";
      return fetchWeather(city);
    },
    render: ({ args, result }) => <WeatherCard city={args.city} weather={result} />,
  },
});

Register it with Tools({ toolkit }), the same as on the web:

import type { ReactNode } from "react";
import {
  AssistantRuntimeProvider,
  AuiConfig,
  Tools,
  useLocalRuntime,
} from "@assistant-ui/react-native";
import toolkit from "./toolkit";
import { modelAdapter } from "./modelAdapter";

const config = AuiConfig({ tools: Tools({ toolkit }) });

const App = ({ children }: { children: ReactNode }) => {
  const runtime = useLocalRuntime(modelAdapter);
  return (
    <AssistantRuntimeProvider runtime={runtime} config={config}>
      {children}
    </AssistantRuntimeProvider>
  );
};

How it works

withAui points Metro's babelTransformerPath at this package's transformer, which runs the "use generative" compiler and then delegates to your project's existing transformer (Expo's or React Native's).

The build target follows Metro's environment: the device app gets the client build (schema + render + frontend execute), while an Expo Router +api route (bundled for a server environment) gets the server build (schema + backend execute). This mirrors @assistant-ui/next and @assistant-ui/vite.

See the Tools docs for the full authoring API.