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

@getik-public/cli

v1.5.5

Published

Getik CLI

Readme

Getik CLI

@getik-public/cli is a collection of scripts meant to ease the development flow. For available scripts read further.

How to use the cli

Add next line in your package.json file under devDependencies:
"@getik-public/cli": "X.Y.Z" or simply run npm i @getik-public/cli@latest --save-dev.

Available scripts

mobile-build

Usage: getik-cli mobile-build [-p, --platform] [-e, --environment] [--syncOnly] [--aab] [--upload]

Example: getik-cli mobile-build -p android -e getikDebug --syncOnly
Example: getik-cli mobile-build --platform ios --environment getik --upload

| Option | Required | Values | Description | |---------------------|----------|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | -p, --platform | NO | android, ios | Platform to build for. | | -e, --environment | YES | <string>, <string>Debug | While environment can be any name, be consistent and use these: getik, vbox, qa, prod. Every environment must have a pair for debug build, so have these environments also defined: getikDebug, vboxDebug, qaDebug, prodDebug | | --syncOnly | NO | - | For development only, if you need to apply javascript build, or a new plugin was added. This will not go further to trigger an android or ios build script. If --platform missing it will run cap sync for all platforms. | | --aab | NO | - | For --platform android only. Build aab file instead of apk file. | | --upload | NO | - | For --platform ios only. Instant upload to store after build, if successful. | | --releaseTesting | NO | - | For --platform ios only. Will apply *-export-options.testing.plist file instead of *-export-options.plist. |

web-build

Usage: getik-cli web-build [-e, --environment] [--syncOnly]

Example: getik-cli web-build -e getik --syncOnly
Example: getik-cli web-build -e getik

| Option | Required | Values | Description | |-----------------------|----------|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | -e, --environment | YES | <string> | While environment can be any name, be consistent and use these: getik, vbox, qa, preprod, prod. | | --syncOnly | NO | - | For development only, it will create a file named version.ts with version found in package.json. Use this version in all environment.ts files. This will not go further to trigger the actual build script. | | --includeDemo | NO | - | Use this flag to also include the demo build variant for the selected environment. | | --includeFallback | NO | - | Use this flag to also include the fallback build variant for the selected environment. |

upload-to-getik-cloud

Usage: getik-cli upload-to-getik-cloud ./path/to/my-file.apk --host awesome.host.net --useCommitHash

Use this command to upload apk files to getik cloud. If successful, in command line you will find a direct link to fresh uploaded file alongside a link to the full list.
Run this command from the root of the project, as it tries to look for project name in package.json file. Project name will be used as file name.
Use --useCommitHash option if git hash needs to be added to the file name. This parameter is optional.