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 🙏

© 2024 – Pkg Stats / Ryan Hefner

expo-native-asset

v0.0.1

Published

Bundle images to the native iOS asset catalog

Downloads

3

Readme

expo-native-asset

Bundle images to the native iOS Images.xcassets asset catalog

Motivation

When using Expo Router (or the underlying React Navigation library), you have the option to swap out the native header back image.

The recommended way to add a custom back image is via Expo's official expo-asset package. However, I've found that on iOS builds there is an FONC (Flash of Native Content) before the custom image is swapped in.

This config plugin bundles your images natively in your asset catalog, so they are available at build time for your app to use. No more FONC!

Installation

  1. Install the expo-native-asset library:

    yarn add expo-native-asset
  2. Add the desired assets to your project repo (we recommend in assets):

    |- assets/
       |- images/
          |- chevron-left.png
          |- [email protected]
          |- [email protected]
          |- chevron-right.png
  3. Add the desired assets to your app.json (or app.config.js) file:

    {
       "plugins": [
          [
             "expo-native-asset",
             {
                "assets": [
                   {
                      "type": "imageset",
                      // The plugin will automatically pick up your @2x and @3x files if they both exist
                      "path": "./assets/images/chevron-left.png"
                   },
                   {
                      "type": "imageset",
                      "path": "./assets/images/chevron-right.png"
                   }
                ]
             }
          ]
       ]
    }
  4. Rebuild your app as described in the "Adding custom native code" guide

  5. Start using the newly defined asset in your code:

    <Stack
      screenOptions={{
        headerBackImageSource: { uri: "chevron-left", width: 20, height: 20 },
      }}>

Contributing

Check out our Contributing guide for more information on reporting issues, submitting feedback, or contributing code.

Setup

To set up the repository locally on your machine, follow these steps:

  1. Install the project dependencies:

    yarn
  2. Create a new build:

    yarn build

Testing

To test that the project works, use the example app in the example directory:

  1. In the root of this repo, run the build server:

    yarn build
  2. In the example directory, rerun the prebuild process:

    EXPO_DEBUG=1 expo prebuild --clean
  3. Confirm the plugin works as expected!