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

pixelize-native-library

v1.2.0

Published

Pixelize mobile design library — React Native / Expo. The mobile counterpart to pixelize-design-library.

Readme

pixelize-native-library

Pixelize's React Native / Expo design library — the mobile counterpart to pixelize-design-library (web).

npm i pixelize-native-library
import { PixelizeProvider } from "pixelize-native-library/theme";
import { Button } from "pixelize-native-library/button";

Why subpath imports

pixelize-native-library/button pulls Button's module subtree and nothing else. Charts, the date picker, and the table never enter your bundle unless you import them.

This is not tree-shaking. Metro's tree-shaking is experimental, production-only, and enabled by a flag the consumer app sets — a library can't turn it on. Package Exports have been stable in Metro since 0.79 and work in dev and prod, on bare RN and Expo, with zero config in your app.

Docs

  • Component list and props: registry.json (generated)
  • Contributing / API contract: CLAUDE.md
  • Playground: example/ (Expo)

Theme

Themes and colours are shared with web by hand-copying one folder: src/theme/tokens/. It is byte-identical across both repos and hash-gated in CI (.tokens.sha256). Anything platform-specific lives in src/theme/platform/, which is never copied.