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

@keg-hub/appetite

v1.0.1

Published

appetize.io api wrapper

Readme

Overview

A node-js wrapper around the appetize api

Example

const { upsert } = require('@keg-hub/appetite')

// Updates an existing build if one is found, otherwise uploads a new one
const response = await upsert({
  // appetize api token
  token: '123456',

  // upload or update a build using these parameters
  url: 'some.url.to.simulator.build.com'
  platform: 'ios',
  meta: {
    branch: 'my-branch',
  },
  ...*: <any other update/upload field (see the Appetize docs)>,

  // searches for a build where platform=ios and note='{"branch":"my-branch"}'
  search: {
    platform: 'ios',
    meta: {
      branch: 'my-branch',
    }
  }
})

Usage

Install

yarn add @keg-hub/appetite

Upload

const { upload } = require('@keg-hub/appetite')

// set either url or filePath, not both
const response = await upload({
  url: <url to your simulator build>
  filePath: <system file path to your simulator build>,
  platform: <ios or android>,
  token: <your appetize api token>
  note: <note field>,
  meta: <object to be stringified for the note field, unless "note" param was defined>,
  ....rest: <any other fields to include in the post form>
})

Update

const { update } = require('@keg-hub/appetite')

// set either url or filePath, not both
const response = await update({
  publicKey: <public key of app build to update>,
  url: <url to your simulator build>
  filePath: <system file path to your simulator build>,
  platform: <ios or android>,
  token: <your appetize api token>
  note: <note field>,
  meta: <object to be stringified for the note field, unless "note" param was defined>,
  ....rest: <any other fields to include in the post form>
})

Upsert

const { upsert } = require('@keg-hub/appetite')

// set either url or filePath, not both
const response = await upsert({
  token: <your appetize api token>,
  search: <fields to search for existing builds. Same as `search`>
  ...*: <fields used for uploading/updating a build. Same params as `upload`>
})

Search

const { search } = require('@keg-hub/appetite')

// searches for all builds matching the parameters
const builds = await search({
  note: <note field of an existing app build to search by>,
  meta: <note fields of an existing app build to search by>,
  platform: <ios or android>,
  token: <your appetize api token>
})

Get

const { get } = require('@keg-hub/appetite')

// set either url or filePath, not both
const response = await get({
  publicKey: <public key of app build to get>,
  token: <your appetize api token>
})

Remove

const { remove } = require('@keg-hub/appetite')

// set either url or filePath, not both
const response = await remove({
  publicKey: <public key of app build to delete>,
  token: <your appetize api token>
})

Notes

  • Methods like search accept an optional meta parameter
  • If this parameter is included, it will treat the "note" field as a json object string
  • For example, search will look for an existing build whose "note" value is a json object string containing the fields included in meta
  • upload and update will stringify the meta object and set that as the value of the "note" field in the uploaded/updated build

Testing

  • Unit: yarn test
  • Functional: yarn test:e2e
    • this test will require you to set some ENVS
      • it's easiest to create a .env file in the repo's root directory
      • see the example.env file for the expected variables to put there
    • this will test creating, searching, updating, and deleting a single app using your Appetize account, live