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-releaser

v3.2.0

Published

A simple cli to update your expo configurations for a new release

Downloads

7

Readme

Expo Releaser

A simple cli to update your expo configurations for a new release

Usage

expo-releaser -r 1.3.2

The command will save changes to your expo configuration files like so:

app.config.js

{
-    version: "1.3.1",
+    version: "1.3.2",
     ios: {
-        buildNumber: "14",
+        buildNumber: "15",
     },
     android: {
-        versionCode: 12,
+        versionCode: 13,
     }
}

eas.json

{
  "build": {
     "staging": {
-      "releaseChannel": "staging-1.3.1",
+      "releaseChannel": "staging-1.3.2",
     },
     "production": {
-      "releaseChannel": "production-1.3.1",
+      "releaseChannel": "production-1.3.2",
     }
  }
}

package.json

{
   "name": "my-app",
-  "version": "1.3.1",
+  "version": "1.3.2",
}

Unversioned release channels

If you want your release channels to simply be staging instead of staging-1.3.1 or production instead of production-1.3.1 you should pass the -i flag to ignore release channels in your updates

Review the changes. If they look good then commit and begin your deployment workflow.

License

expo-releaser is Copyright © 2022 GorillaBot Labs, LLC. It is free software, and may be redistributed under the terms specified in the LICENSE file.

About GorillaBot Labs

GorillaBot Labs

expo-releaser is maintained and funded by GorillaBot Labs, LLC.

We help bold entrepreneurs solve big problems with software. Hire us to design, develop, and grow your product.