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

@forthtilliath/expo-release-updates

v0.3.0

Published

Self-update a sideloaded Android Expo app from its GitHub Releases: check the latest release, show a release history, download and trigger the install of a new APK. No backend needed — just a GitHub repo that publishes an `.apk` asset on each release.

Readme

@forthtilliath/expo-release-updates

Self-update a sideloaded Android Expo app from its GitHub Releases: check the latest release, show a release history, download and trigger the install of a new APK. No backend needed — just a GitHub repo that publishes an .apk asset on each release.

Install

npm install @forthtilliath/expo-release-updates expo-file-system expo-intent-launcher

Or, from within this monorepo, as a workspace dependency:

{
  "dependencies": {
    "@forthtilliath/expo-release-updates": "workspace:*"
  }
}

expo-file-system and expo-intent-launcher are peer dependencies — install them in the consuming app if not already present.

Usage

Each function is its own module — import the file you need directly, or use the barrel to pull everything from a single import:

import { compareVersions } from "@forthtilliath/expo-release-updates/compareVersions";
import {
  fetchLatestRelease,
  fetchReleaseHistory,
} from "@forthtilliath/expo-release-updates/githubReleases";
import { downloadAndInstallApk } from "@forthtilliath/expo-release-updates/downloadAndInstallApk";
import { parseChangelogNotes } from "@forthtilliath/expo-release-updates/parseChangelogNotes";

// Or, everything at once:
import {
  compareVersions,
  fetchLatestRelease,
  fetchReleaseHistory,
  downloadAndInstallApk,
  parseChangelogNotes,
} from "@forthtilliath/expo-release-updates";

Avoid the barrel under Jest (or any other CommonJS require consumer). export * from re-exports are evaluated eagerly on require() — unlike Metro's ESM bundling, there's no tree-shaking to skip the unused ones. Requiring the barrel from any file, even one that only wants compareVersions, pulls in downloadAndInstallApk's module graph too, including native-module imports (expo-file-system, expo-intent-launcher) that don't exist in a Jest environment — this throws at require time, not just at runtime for unused code. Deep imports only ever load the one module you asked for, so they don't have this problem in any environment.

compareVersions(a, b)

Compares two "x.y.z" version strings, segment by segment. Returns -1 if a < b, 0 if equal, 1 if a > b.

compareVersions("1.2.0", "1.10.0"); // -1 (numeric, not lexicographic)
compareVersions("2.0.0", "1.9.9"); // 1
compareVersions("1.2.3", "1.2.3"); // 0

fetchLatestRelease({ owner, repo })

Fetches the latest GitHub release and its .apk asset. Returns null if the latest release has no .apk attached; throws if the GitHub API request fails.

const release = await fetchLatestRelease({ owner: "acme", repo: "app" });
if (release && compareVersions(release.version, currentVersion) > 0) {
  // an update is available: release.version, release.notes, release.apkUrl
}

fetchReleaseHistory({ owner, repo, limit? })

Fetches the most recent releases (version, notes, publish date), most recent first. limit defaults to 10 — useful for a "release history" / "what's new" screen.

const history = await fetchReleaseHistory({
  owner: "acme",
  repo: "app",
  limit: 5,
});
// [{ version: "1.11.0", notes: "### Added\n- ...", publishedAt: "2026-07-30T..." }, ...]

downloadAndInstallApk({ apkUrl, fileName, onProgress? })

Downloads an APK to the app's cache directory and triggers the Android install-package intent. Android only — there is no iOS equivalent (sideloading isn't possible there).

await downloadAndInstallApk({
  apkUrl: release.apkUrl,
  fileName: "myapp-update.apk",
  onProgress: (fraction) => setProgress(fraction),
});

parseChangelogNotes(notes)

Parses a small subset of Markdown (### heading, - item, **bold**) commonly found in GitHub release notes into a list of typed blocks (heading / item / text, each with bold-aware segments), ready for a UI layer to render without a full Markdown dependency. Pair it with @forthtilliath/react-native-kit's ChangelogNotes component to render the result directly.

parseChangelogNotes("### Added\n- **Auto-backup**: saves every 5 minutes.");
// [
//   { type: "heading", text: "Added" },
//   {
//     type: "item",
//     segments: [
//       { text: "Auto-backup", bold: true },
//       { text: ": saves every 5 minutes.", bold: false },
//     ],
//   },
// ]

Scripts

pnpm run dev            # tsc --watch -> dist/
pnpm run build          # tsc -> dist/
pnpm run check-types    # tsc --noEmit
pnpm run lint           # eslint
pnpm run test           # vitest run
pnpm run test:watch     # vitest

Built to dist/ (see the exports field in package.json), so run pnpm run build (or dev) after source changes for consumers to see them.