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

@torah-anytime/standard-version-expo

v0.1.6

Published

Standard Version Expo bumpers

Downloads

2

Readme

Standard Version Expo Bumpers

Standard Version custom updaters for Expo

When publishing bare workflows using Expo Publish, Expo does not make sure that updates are only pushed to devices which have the correct binary. This can cause old app versions, which do not have the required native dependencies, to receive new javascript bundle updates.

The recommended solution is to use Runtime Versions. However, Runtime Versions is not compatible with the Expo classic build system (expo build).

The second option is to use Expo Channels.

This module contains bumpers which assist in keeping both methods in sync with the app version number.

npm install @torah-anytime/standard-version-expo

Update Expo Runtime Version

Note from the Expo docs: Custom runtime versions are not supported on the classic build system (expo build); these apps will always use the SDK version as the basis for determining runtime compatibility.

WARNING: The Android Manifest (android/app/src/main/AndroidManifest.xml) must already contain <meta-data android:name=“expo.modules.updates.EXPO_RUNTIME_VERSION” android:value=“<any value>"/>. Otherwise it will throw an error.

// .versionrc.js
module.exports = {
  bumpFiles: [
    // ...
    {
      filename: "ios/TorahAnyTime/Supporting/Expo.plist",
      updater: require("@torah-anytime/standard-version-expo/dist/ios/native/runtime-version"),
    },
    {
      filename: "android/app/src/main/AndroidManifest.xml",
      updater: require("@torah-anytime/standard-version-expo/dist/android/native/runtime-version"),
    },
  ],
};

Update Expo Release Channel

WARNING: The Android Manifest (android/app/src/main/AndroidManifest.xml) must already contain <meta-data android:name=“expo.modules.updates.EXPO_RELEASE_CHANNEL” android:value=“<any value>"/>. Otherwise it will throw an error.

To automatically update the iOS and Android Expo release channel to match the app version install this package and add the bump files:

// .versionrc.js
module.exports = {
  bumpFiles: [
    // ...
    {
      filename: "ios/<YourAppName>/Supporting/Expo.plist",
      updater: require("@torah-anytime/standard-version-expo/dist/ios/native/release-channel"),
    },
    {
      filename: "android/app/src/main/AndroidManifest.xml",
      updater: require("@torah-anytime/standard-version-expo/dist/android/native/release-channel"),
    },
  ],
};

To test if your configuration works as expected, you can run standard version in dry mode. This shows you what will happen, without actually applying the versions and tags.

npx standard-version --dry-run

Credit

Inspired by: https://github.com/brettdh/standard-version-expo