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

@mayurajs/deploy-cloudrun

v1.2.0

Published

Google Cloud Run as a mayura deploy target: a migration job, then the server and an always-on worker as services.

Readme

@mayurajs/deploy-cloudrun

Google Cloud Run as a mayura deploy target. A migration job runs to completion, then the server and an always-on worker deploy as services, all from one image, with gcloud.

npm install --save-dev @mayurajs/deploy-cloudrun
mayura deploy init --target cloudrun --apply
# In mayura.deploy.json: "image" is an Artifact Registry repository and targets.cloudrun.project is the project id.
mayura deploy --target cloudrun               # prints the plan and its digest
mayura deploy --target cloudrun --apply --confirm <digest>

A release runs these steps, stopping at the first failure:

  1. gcloud projects describe, so a missing login or project stops it.
  2. The image is built with Cloud Build, or with your Docker and pushed (build: "local").
  3. The <name>-migrate job is updated to the release's image, then run and waited for (--execute-now --wait, no retries). A failed migration stops the release.
  4. <name>-server deploys with CPU always allocated and at least one instance, since agent runs continue after a response. It gets a /readyz startup probe and a one-hour request timeout for streams.
  5. <name>-worker deploys as an internal, non-public service that serves only its probes, also always running.

Notes:

  • Secrets come from Secret Manager with --set-secrets. By default, DATABASE_URL and every name in env read a secret of the same name at latest; map others with secrets, such as { "OPENAI_API_KEY": "openai-key:3" }. Values never appear in a plan.
  • Settings in mayura.deploy.json under targets.cloudrun:
    • project, and region (us-central1);
    • build (cloud-build or local) and secrets;
    • cloudSqlInstance (project:region:instance, for the Cloud SQL connector) and serviceAccount;
    • public (true: the server authenticates requests itself);
    • serverMinInstances and workerInstances (1 each).
  • Credentials: gcloud uses its own login (gcloud auth login, or a service account in CI); Mayura reads neither. On Windows gcloud is a .cmd script, which mayura deploy runs through cmd.exe with checked, quoted arguments.

See Deploy with mayura deploy. Apache-2.0.