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

@sil/app-release

v0.3.0

Published

Shared iOS app release automation for screenshots, promo videos, metadata, and App Store uploads.

Readme

@sil/app-release

Shared release automation for iOS app families.

The package owns the repeatable release logic. Each product repo owns its own config, copy, screenshots, launch hooks, signing, Apple IDs, and output paths.

Install

Use from a repo with npx:

npx @sil/app-release --config apps/chess/release/ios.json --mode screenshots
npx @sil/app-release --config apps/chess/release/ios.json --mode promo-video
npx @sil/app-release --config apps/chess/release/ios.json --mode all

For local development:

node /Users/silvandiepen/Repositories/_projects/app-release/app-release.mjs --config apps/chess/release/ios.json --mode preflight

All Apps

Add a repo-owned release.config.json:

{
  "apps": [
    { "slug": "chess", "releaseConfig": "apps/chess/release/ios.json" },
    { "slug": "reversi", "releaseConfig": "apps/reversi/release/ios.json" }
  ]
}

Relative releaseConfig paths resolve from the manifest location. In normal product repos that means paths are usually relative to the repo root.

Then run:

npx -p @sil/app-release app-release-all --mode screenshots
npx -p @sil/app-release app-release-all --mode promo-video --apps chess,reversi

Modes

  • preflight: print paths, config status, upload readiness, and tool availability.
  • validate / verify: run the configured app validation command.
  • screenshots: build the simulator app and capture configured screenshots.
  • site-screenshots: capture screenshots into site/public/screenshots/apps/<app>.
  • promo-video / promo-videos / videos: record or compose promo/App Preview videos.
  • archive: create an Xcode archive and optional IPA export.
  • upload-build: upload a configured IPA with xcrun altool.
  • prepare-metadata: export repo-owned metadata JSON to Fastlane Deliver format.
  • upload-metadata: upload metadata with Fastlane Deliver.
  • prepare-screenshots: copy screenshots into Fastlane Deliver screenshot layout.
  • upload-screenshots: upload screenshots with Fastlane Deliver.
  • distribute: upload build, metadata, and screenshots.
  • all: validate, screenshots, archive, prepare metadata, prepare screenshots.

Every runnable mode checks its own requirements before doing work. Missing tools, paths, environment variables, or config fields are reported per module, for example screenshots, promo-video, archive, or upload-metadata.

Config Ownership

Keep config in the consuming repo.

Recommended per-app file:

apps/<app>/release/ios.json

The app config owns:

  • Xcode project, scheme, bundle ID, product name.
  • App Store Connect Apple ID.
  • validation command.
  • screenshot devices, locales, scenarios, color modes, launch args/env, and output folder.
  • metadata source folder.
  • promo video segments.
  • archive/export/upload settings.

For a full setup checklist, use docs/setup-new-project.md. For every config field currently supported, use docs/config-reference.md.

Screenshot Hooks

Apps can be driven with launch args:

{
  "launchArgs": ["--ui-testing", "--screenshot", "menu"]
}

Or simulator child environment variables:

{
  "env": {
    "MAZZI_SCREENSHOT": "1",
    "MAZZI_SCREENSHOT_ROUTE": "settings"
  }
}

Keys are automatically prefixed with SIMCTL_CHILD_ unless they already start with it.

External Tools

Required for common local capture:

  • Xcode command line tools
  • XcodeGen, when projects are generated from project.yml
  • iOS Simulator runtime

Required for promo videos:

  • FFmpeg
  • ImageMagick when using title, card, or cta segments

Required for uploads:

  • Fastlane for metadata/screenshot upload
  • App Store Connect API credentials for build upload