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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@percolate/press

v1.2.23

Published

CI release tooling

Readme

@percolate/press

CI release tooling

press <command>

Commands:
  press push <image>  Push docker image to ECR
  press release       Create and finalize a Sentry release
  press sentry-cli    sentry-cli proxy with master gating and project injection

Options:
  --version   Show version number                                      [boolean]
  -h, --help  Show help                                                [boolean]

Usage

yarn add @percolate/press --dev
npx press -h

Development

yarn watch

yarn run for all options.

Testing profiles

Given the following AWS config/credentials:

# ~/.aws/config
[profile my_profile]
role_arn = ...
source_profile = default
region = us-east-1
# ~/.aws/credentials
[default]
aws_access_key_id = ...
aws_secret_access_key = ...
npx press push --profile=my_profile --region=us-east-1

Important: aws-sdk supports profiles for ~/.aws/credentials but not ~/.aws/config which is why the --region needs to be specified.

Containerized version

A containerized version of @percolate/press can be found on our private registry 667005031541.dkr.ecr.us-west-1.amazonaws.com/percolate/blend/press:latest

Usage example

Here's an example of a CircleCI config which leverages percolate/blend/press to push my_image. test and build can be parallelized to speed up the whole workflow.

version: 2.1

executors:
    press:
        docker:
            # please replace `latest` with specific version
            - image: 667005031541.dkr.ecr.us-west-1.amazonaws.com/percolate/blend/press:latest

jobs:
    test: # custom tests go here

    build:
        executor: press
        steps:
            - checkout
            - setup_remote_docker
            # VERSION must match `press release --version=${VERSION}` (defaults to `${CIRCLE_SHA1}`)
            - run: docker build --tag my_image . --build-arg VERSION=${CIRCLE_SHA1}
            - run: docker save my_image > /tmp/my_image.tar
            - persist_to_workspace:
                  root: /tmp
                  paths:
                      - my_image.tar
    release:
        executor: press
        steps:
            - checkout
            - attach_workspace:
                  at: /tmp
            - setup_remote_docker
            - run: press push my_image --fromArchive=/tmp/my_image.tar
            - run: press release

workflows:
    version: 2
    my_repo:
        jobs:
            - test
            - build
            - release:
                  # context contains sentry org, token, and uri as env vars
                  context: sentry
                  requires:
                      - test
                      - build

building and publishing

@percolate/press relies on other packages in this monorepo (ex. @percolate/cli-utils). By splitting the build process, we're able to simplify the docker build logic drastrically and optimize the image to only include runtime dependencies.

Build flow found in .circleci/config.yml for details.:

  1. build and publish @percolate/press to NPM:
    1. install blend dependencies to build packages
    2. build @percolate/press and its dependencies
    3. publish @percolate/press NPM.
  2. build and publish percolate/blend/press to ECR:
    1. build docker image off latest @percolate/press version
    2. leverage @percolate/press to push image

See root README.md