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 🙏

© 2025 – Pkg Stats / Ryan Hefner

expo-signed

v1.0.0

Published

Effortlessly configure signing for Android builds in Expo projects during the prebuild process.

Readme

expo-signed

A Plugin for Signing Android Builds on Expo Prebuild

Effortlessly configure signing for Android builds in Expo projects during the prebuild process.

How It Works

  • Step 1: Updates the gradle.properties file to include signing configurations.
  • Step 2: Modifies the build.gradle file to switch from debug signing to release signing.
  • Step 3: Adds a release signing block to the build.gradle file if it doesn’t already exist.
  • Step 4: Copies the keystore file to the android > app directory for signing during the build process.

Resources


Features

  • Automatic Configuration: Updates android > gradle.properties to include the specified signing properties if they don’t already exist.
  • Signing Configuration: Replaces signingConfig signingConfigs.debug with signingConfig signingConfigs.release under android.buildTypes.release in android > app > build.gradle.
  • Release Block Addition: Adds the release block with the specified properties to android.signingConfigs in android > app > build.gradle if it doesn’t exist.
  • Keystore File Handling: Copies the specified .keystore file (defined by store_file.value) from the keystorePath to the android > app folder.

Prerequisites

Before using expo-signed, generate a private signing key and follow these steps:

  1. Generate a Key:
    Use keytool to create a private signing key. Follow the instructions provided in the React Native documentation on signed APKs.

  2. Place the Keystore File:
    Add the generated keystore file to your project directory.


Installation

To install and configure the plugin:

1. Define the Keystore Location

  • Place the .keystore file in your project, and set the folder path (keystorePath) and file name (store_file.value) in the configuration.

2. Update app.json

Add the plugin configuration to your app.json as follows:

"plugins": [
    ...
    [
        "expo-signed",
        {
            "store_file": {
                "key": "MY_UPLOAD_STORE_FILE",
                "value": "my-upload-key.keystore"
            },
            "key_alias": {
                "key": "MY_UPLOAD_KEY_ALIAS",
                "value": "my-key-alias"
            },
            "store_password": {
                "key": "MY_UPLOAD_STORE_PASSWORD",
                "value": "************"
            },
            "key_password": {
                "key": "MY_UPLOAD_KEY_PASSWORD",
                "value": "************"
            },
            "keystorePath": "./src/assets"
        }
    ],
    ...
]

By following the above steps, you’ll be able to sign your Android builds seamlessly with expo-signed.