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

@tamagui/native-registry

v3.1.4

Published

Generic native style registry: zero-re-render style updates via Fabric ShadowTree commits

Readme

@tamagui/native-registry

@tamagui/native-registry is the native engine for Tamagui's experimental theme fast path. It links eligible Fabric views to a small C++ registry and applies theme changes through one ShadowTree commit without re-rendering those views in React.

The package supports React Native 0.82 and newer. It uses react-native-nitro-modules, so adding it requires rebuilding the native app.

Enable the experiment

Install both native packages:

bun add @tamagui/native-registry react-native-nitro-modules

Enable compiler output in tamagui.build.ts:

import type { TamaguiBuildOptions } from 'tamagui'

export default {
  config: './tamagui.config.ts',
  components: ['tamagui'],
  experimental: {
    nativeFastPath: true,
  },
} satisfies TamaguiBuildOptions

Install the engine before the themed application tree mounts:

import * as nativeRegistry from '@tamagui/native-registry'
import { setNativeStyleEngine } from 'tamagui'

if (nativeRegistry.isAvailable()) {
  setNativeStyleEngine(nativeRegistry)
}

Then rebuild the iOS and Android applications. A Metro reload cannot add the native module to an existing binary.

This API is experimental. Keep the flag off for production applications unless you can run the native correctness suite for the React Native versions and list implementations your application ships.

Fallback behavior

The flag defaults to false. With the flag off, native compiler output is unchanged. With the flag on but no engine installed, emitted components use the existing theme hook and React render path. Web output is unchanged in both cases.

The registry coexists with Tamagui's existing DynamicColorIOS optimization. It does not replace or remove that path.