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

@rukkiecodes/native

v0.1.0

Published

FusionUI for mobile — Expo + React Native components that mirror the web contracts, sharing tokens and the signature visual identity (liquid glass via Skia/SKSL).

Readme

@rukkiecodes/native

FusionUI for mobile — Expo + React Native components that mirror the web component contracts (same names, props, variants, states), share the same design tokens, and carry the signature liquid glass identity to native via Skia.

What's shared with @rukkiecodes/vue: token values, component API (names, props, variants, states), interaction/a11y semantics, and the visual identity. What's reimplemented: the rendering code (RN instead of Vue). <FButton variant="primary" loading> should feel identical on web and mobile.

Install

npx expo install @shopify/react-native-skia react-native-reanimated
npm i @rukkiecodes/native @rukkiecodes/tokens
# iOS 26 real Liquid Glass (optional): npx expo install expo-glass-effect

Usage

import {
  FusionProvider,
  FButton,
  FCard,
  FInput,
  FSwitch,
  LiquidGlassView,
} from '@rukkiecodes/native'

export default function App() {
  return (
    <FusionProvider theme="light">
      <FCard>
        <FInput label="Email" placeholder="[email protected]" />
        <FButton variant="elevated" color="primary" onPress={save}>
          Save
        </FButton>
        <FSwitch value={on} onValueChange={setOn} />
      </FCard>

      <LiquidGlassView radius={28} options={{ depth: 16, chromaticAberration: 0.4 }}>
        <Text>Frosted toolbar</Text>
      </LiquidGlassView>
    </FusionProvider>
  )
}

Component parity

| Web (@rukkiecodes/vue) | Native (@rukkiecodes/native) | Shared contract | | ------------------------ | ------------------------------ | ---------------------------------------------------------------------------------------------- | | <FBtn> | <FButton> | variant (elevated/flat/tonal/outlined/text), color, size, loading, disabled, block | | <FCard> | <FCard> | flat, padding, radius; Vuesax soft shadow | | <FInput>/<FField> | <FInput> | label, value/onChangeText, disabled, error, message, color | | <FSwitch> | <FSwitch> | value/onValueChange, color, disabled | | <FGlass> | <LiquidGlassView> | radius, glass options (bezel/depth/ior/…); same SDF→Snell engine |

The FButton variants are a guaranteed subset of the web allowedVariants (enforced by a unit test). More MVP components (Checkbox/Radio, Modal, Navbar, Tooltip) are a fast-follow.

Liquid glass on native

One physics model, two backends — the same engine/liquid-glass core as the web package (SDF → surface normal → Snell refraction), here driving the GPU:

  • iOS 26+expo-glass-effect (UIGlassEffect — system-composited, live backdrop sampling, free).
  • Android / older iOS@shopify/react-native-skia BackdropFilter running GLASS_SKSL — the same refraction math transliterated to SKSL, with chromatic aberration at the rim.

The Android backdrop-sampling constraint is physics, not a bug: an app can't read pixels behind an arbitrary native view, so the Skia path refracts what's inside its canvas — render the backdrop in-canvas, or snapshot it with useBackdropSnapshot.

Theme

FusionProvider feeds the @rukkiecodes/tokens native output (durations in ms, dimensions as numbers, shadows as {color,offsetX,offsetY,blur,opacity} objects). useFusionTheme() reads it; shadowStyle(token, elevation) maps a shadow token to RN's iOS shadow* + Android elevation in one call.

Verification

typecheck + Vitest unit tests cover the pure layers: token parity (the native palette equals the web palette, from one source), the shared glass engine math (plateau refracts to zero), the shadow mapping, and the FButton↔FBtn variant subset. Component rendering and the live glass effect require a device/simulator (jest-expo / EAS) — out of scope for CI here.