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

@artsy/palette-mobile

v23.2.0

Published

Artsy's design system for React Native

Readme

Palette Mobile

@artsy/palette-mobile npm version CircleCI

Artsy's Design System on Mobile

Meta

What is Palette?

Palette is a collection of primitive, product-agnostic elements that help encapsulate Artsy's look and feel at base level. This project is intended to be used across our digital product portfolio.

Does my component belong in Palette?

If the component applies to Artsy as a brand and can/will be used across multiple digital products, then Palette is a great place for it. If it's highly product specific then it's best to leave the component where it's used. We can always move things later!

Looking for home view components?

The server-driven home view architecture launched in Eigen (Q4 2024) makes use of a standard library of home view section components.

Those components may make use of palette-mobile primitives, but they are not defined here. Instead they are defined directly in Eigen and documented in this Notion page.

If the above guidance still doesn't give you a good sense of what to do, please join the mobile practice meetings.

How to install

  • Install main library
yarn add @artsy/palette-mobile
  • Install native peer deps
yarn add react-native-haptic-feedback react-native-linear-gradient react-native-reanimated react-native-svg react-native-safe-area-context

How to contribute

If you'd like to add a new component to Palette please create an issue using the component spec template. That'll give both design and engineering a chance to peek at the proposal and provide feedback before moving forward.

Local development

mise install

If you are still using asdf:

asdf install

Set up using:

yarn install
yarn setup:artsy
yarn install:all

Run using:

yarn ios

or

yarn android

Deployment

Building and Deploying iOS to TestFlight

Local Build (requires Fastlane):

brew install gh # First time only
brew install fastlane  # First time only
cd Example
yarn beta:ios

The build will run locally and will create a "Submission Version Build iOS App Store submission" entry on https://expo.dev/accounts/artsy_org/projects/palettemobile

Cloud Build via GitHub Actions:

cd Example
yarn beta:ios:ci

Or trigger manually from GitHub Actions

The build will run a GitHub Workflow and will create a "Submission Version Build iOS App Store submission" entry on https://expo.dev/accounts/artsy_org/projects/palettemobile

Publishing Over-the-Air Updates

After building and deploying to TestFlight, you can publish JavaScript/asset updates instantly without App Store review:

cd Example
yarn update:beta

Users will receive the update on their next app launch. OTA updates are ideal for bug fixes, minor features, and content changes that don't require native code changes.

Developing Features using Local Versions of Palette

When developing new components in Palette, it's often useful to test those components in consuming apps (such as Eigen). However, due to the poor support for symlinks in React Native, this can be difficult. Enter yalc. Yalc is a mini package manager that one can publish to and install from, which makes it easy to test code in realtime from outside of your app.

Note: @artsy/palette-mobile uses Storybooks for developing features; work there first! Then, when ready (and if necessary), test your code locally using the flow described below. You can also publish npm canary releases from the palette-mobile repo by attaching a canary label to your PR.

Setup

  • Install yalc globally:
yarn global add yalc
  • Navigate to palette-mobile in the terminal and start the watcher:
cd palette-mobile
yarn local-palette-dev
  • Navigate back to Eigen and link:
cd eigen
yarn local-palette-dev
yarn start

This will update package.json to point at the yalc-published version of palette.

  • When done developing your local palette feature, be sure to unlink:
yarn local-palette-dev:stop

Repos consuming Palette Mobile

You can add this library using yarn add @artsy/palette-mobile. Don't forget to also add all the peerDependencies to your project.

For connecting Palette to a locally running version of our mobile apps, see these docs.

About Artsy

This project is the work of designers and engineers at Artsy, the world's leading and largest online art marketplace and platform for discovering art. One of our core Engineering Principles is being Open Source by Default which means we strive to share as many details of our work as possible.

You can learn more about this work from our blog and by following @ArtsyOpenSource or explore our public data by checking out our API. If you're interested in a career at Artsy, read through our job postings!