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

changesets-mobile

v0.1.2

Published

Changeset wrapper with iOS and Android native version management

Downloads

487

Readme

changesets-mobile

A CLI that wraps @changesets/cli to support iOS and Android native version management. Instead of only bumping package.json, it syncs the new version into your iOS (Info.plist + project.pbxproj) and Android (build.gradle / build.gradle.kts) files automatically.

Installation

npm install --save-dev changesets-mobile

Setup

# If you haven't already, initialise changesets in your repo
npx changeset init

# Then set up changesets-mobile
npx changeset-mobile init --version 1.0.0

init creates a changeset-mobile.config.json in your project root and optionally sets the initial version in package.json.

Commands

changeset-mobile init                    # Interactive setup — creates changeset-mobile.config.json
changeset-mobile init --version 1.0.0   # Same, but also sets the initial version in package.json
changeset-mobile version                 # Runs "changeset version" then syncs into native files

For authoring changesets (describing what changed in a PR), use the standard CLI directly:

npx changeset add

Configuration

Create changeset-mobile.config.json in your project root (the init command does this for you):

{
  "platforms": [
    {
      "platform": "ios",
      "infoPlist": "ios/App/Info.plist",
      "pbxproj": "ios/App.xcodeproj/project.pbxproj",
      "buildNumber": "auto"
    },
    {
      "platform": "android",
      "buildGradle": "android/app/build.gradle.kts",
      "versionCode": "auto"
    }
  ]
}

Config files support // line comments for readability.

Field reference

| Field | Platform | Required | Description | |---------------|----------|----------|-------------| | platform | both | ✅ | "ios" or "android" | | infoPlist | iOS | ✅ | Path to Info.plist | | pbxproj | iOS | ✅ | Path to project.pbxproj | | buildNumber | iOS | ❌ | "auto" to increment, integer to fix, omit to skip | | buildGradle | Android | ✅ | Path to build.gradle or build.gradle.kts | | versionCode | Android | ❌ | "auto" to increment, integer to fix, omit to skip |

How it works

  1. package.json is the source of truth for the version — changesets manages it natively.
  2. After changeset version runs, this tool reads the new version from package.json and writes it into the configured native files.
  3. Build number / versionCode can be auto-incremented or set to a fixed value via config.

iOS

  • Info.plist — updates CFBundleShortVersionString (version) and CFBundleVersion (build number)
  • project.pbxproj — updates MARKETING_VERSION and CURRENT_PROJECT_VERSION across all build configurations

Android

  • build.gradle / build.gradle.kts — updates versionName and versionCode
  • Both Groovy DSL (.gradle) and Kotlin DSL (.kts) syntax are supported

Typical workflow

# On each PR — describe the change type (patch / minor / major)
npx changeset add

# On release (main branch / CI)
npx changeset-mobile version
git add -A && git commit -m "chore: release vX.Y.Z"
git tag vX.Y.Z && git push --follow-tags

License

MIT