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

@springtree/eva-cli

v1.27.4

Published

`eva-cli` is a command line tool that switches an EVA app project between customers and targets. It downloads the assets and configuration of the chosen customer from the EVA customer manager and copies them into the project.

Readme

eva-cli

:evergreen_tree: Purpose

eva-cli is a command line tool that switches an EVA app project between customers and targets. It downloads the assets and configuration of the chosen customer from the EVA customer manager and copies them into the project.

| Field | Value | | ---------------- | --------------------------- | | Customer | SpringTree (internal tool) | | Project | EVA | | Production owner | To be assigned |

:seedling: Getting started

Installation

You can install eva-cli globally or per project.

Globally:

npm install -g @springtree/eva-cli
eva

Per project:

npm install @springtree/eva-cli
npx eva

Authentication

The tool uses a GitHub personal access token to make sure that you have access. Set it up once:

  1. Make sure that you are a member of the SpringTree Solutions organization on GitHub.

  2. Create a personal access token with the read:org and read:user scopes.

  3. Store the token:

    eva set-token --token=TOKEN_HERE

To make sure that a stored token is still valid, run:

eva verify-token

Project configuration

Every project that uses the tool needs an eva-cli.json file at its root. Each key is explained in the eva-cli.json file below.

{
    "version": 1,
    "assets": {
        "appIcon": "src/assets",
        "appLogo": "src/assets",
        "appSplashScreen": "src/assets",
        "appSplashScreenGif": "src/assets",
        "colors": "src/theme",
        "eva-config": "src/assets/env"
    },
    "framework": "ionic",
    "projectName": "eva-companion-app"
}

Usage

When eva-cli.json is in place and your token is stored, run:

eva switch

The tool asks you to pick a customer and a target.

CI setup

In CI you do not run set-token. Run switch:ci instead, with the same flags as switch. The command reads the token from the EVA_SWITCH_TOKEN environment variable, or from the --token flag:

eva switch:ci --token=TOKEN_HERE

The eva-cli.json file

The eva-cli.json file tells the tool which project it runs in and which assets to fetch.

assets key

Each key under assets is the identifier of a project asset in the customer manager. The tool uses the key to find the matching asset that was uploaded for the customer under https://eva-customer-manager.firebaseapp.com/customers/details/:customerId/:projectId. The value is the directory where the tool copies the asset. The copied file is named after the asset id, not after the original file name.

eva-config asset key

The eva-config key is reserved. The tool writes the configuration of the selected target to it, under the file name eva-config.json.

framework key

One of ionic, angular, flutter, react or xcode. The tool uses it to collect usage data and for framework-specific behavior in the future.

projectName key

The name of an existing project under projects in the customer manager. The tool uses it to show only the customers of this project.

postSwitchScriptPath key

A relative path to an executable script. The tool runs it after the switch finished, with eva-cli.json as its argument.

Commands

Usage: eva [options] [command]

Commands:
  set-token [options] [args]     Sets the github personal access token
  switch:ci [options] [args]     Switches environment, to be used in a CI environment
  switch                         Switch eva environment interactively
  verify-token [options] [args]  Verifies the currently saved token or the passed token is valid

Known issues

Windows

On Windows the tool can fail with this error:

ps1 cannot be loaded because running scripts is disabled on this machine

If you see it, change the PowerShell execution policy. See this step-by-step guide or the Microsoft documentation on execution policies.

:hammer: Development

Use the Node.js version in .nvmrc (Node 24).

# Install dependencies
npm install

# Compile TypeScript to bin/
npm run build

# Run the compiled entry point and restart on changes
npm start

# Same, with the Node.js inspector attached
npm run debug

NOTE: npm install refuses package versions that are younger than seven days. See Compliance.

:cool: Technology stack

  • TypeScript, compiled with tsc to bin/
  • Node.js 24
  • commander for the command line interface and enquirer for the interactive prompts
  • firebase-admin to read from the EVA customer manager
  • configstore to store the GitHub token on the machine
  • Published to npm as @springtree/eva-cli

:twisted_rightwards_arrows: Branch strategy and protection

The default branch is master. There are no other long-lived branches.

The master branch is protected by the organization ruleset. It refuses direct pushes, force pushes and deletion. All changes go through a pull request, merged with squash or rebase so that the history stays linear.

Before a pull request can merge:

  • the four supply-chain / * checks (secrets, licences, code, quarantine) must pass
  • changes to the policy files in .github/CODEOWNERS (the compliance workflow, CODEOWNERS itself and licence-exemptions.json) must be reviewed by @springtreesolutions/springtree-admins

:pencil: Commit messages

Commits follow Conventional Commits. This is more than a convention here: release-please reads the commit messages on master to decide the next version number and to write the changelog. A fix: commit makes a patch release, a feat: commit makes a minor release, and a BREAKING CHANGE: footer makes a major release. chore, ci, docs and the like release nothing.

:lock: Compliance

This repository is gated by SpringTree's shared supply-chain workflow (.github/workflows/compliance.yml), which runs four checks on every pull request and a full-history scan weekly:

| Gate | Refuses | | ------------ | ------------------------------------------------------- | | secrets | a credential committed anywhere in the scanned range | | licences | a dependency whose licence is not on the allow-list | | code | a code pattern the ruleset classes as a security defect | | quarantine | missing or incorrect package-cooldown configuration |

A red gate is fixed here, in this repository. What each gate does and which inputs it takes is documented in springtree-ci-workflows.

Packages younger than seven days are refused (min-release-age in .npmrc). That window is a management decision recorded in the secure development standard, not a local preference — raise it there first.

:mag: Before you push

git config core.hooksPath .githooks   # once per clone
brew install gitleaks                 # once per machine

The hook scans the commits you are about to push and refuses the push when gitleaks is not installed. It is feedback, not enforcement: --no-verify skips it and CI does not. Skipping is break-glass.

:up: Deploying

The package is published to npm as @springtree/eva-cli by GitHub Actions using release-please (.github/workflows/release.yml). Nothing is published by hand.

  1. Every merge to master updates a single release pull request with the version bump and changelog since the last release (release-please-config.json, current version in .release-please-manifest.json)
  2. Merging the release pull request creates the tag and GitHub release
  3. The same workflow then builds and publishes the package under the latest dist-tag

Pull requests to master are built by .github/workflows/build.yml, which does not publish.

Publishing uses npm trusted publishing (OIDC), so there is no npm token. The package has a trusted publisher on npmjs.com for this repository, workflow release.yml and environment npm-publish. That GitHub environment only allows deployments from master, so no other branch can publish.