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-azure

v1.2.0

Published

Azure Container Apps as a mayura deploy target: a migration job run to success, then the server and worker apps.

Readme

@mayurajs/deploy-azure

Azure Container Apps as a mayura deploy target, with az. A release runs a migration job to success, then updates the server and the worker and waits for each new revision.

npm install --save-dev @mayurajs/deploy-azure
mayura deploy init --target azure --apply
# In mayura.deploy.json: "image": "<registry>.azurecr.io/refunds" and targets.azure.resourceGroup.
mayura deploy --target azure                  # prints the plan and its digest
mayura deploy --target azure --apply --confirm <digest>

Once, before the first release, create the environment, the two apps and the job from the image. Each runs the image's mayura command with its own arguments and the same environment (secrets as secretref: variables, or Key Vault references):

  • <name>-server: ingress on port 8080, /readyz probes, at least one replica (agent runs continue after a response). Arguments: serve --app dist/app.js.
  • <name>-worker: no ingress, one replica or more. Arguments: worker --app dist/app.js --probe-host 0.0.0.0 --probe-port 9090.
  • <name>-migrate: a manual-trigger job with no retries. Arguments: migrate --app dist/app.js.

A release:

  1. Checks that az is signed in.
  2. Builds the image in Azure Container Registry with az acr build, or with your Docker and pushes it (build: "local").
  3. Points the migration job at the new image, starts it, and waits until it succeeds. A failed migration stops the release before any app changes.
  4. Updates <name>-server and waits until its new revision is running.
  5. Does the same for <name>-worker.

A revision that fails or degrades stops the release.

Settings in mayura.deploy.json under targets.azure:

  • resourceGroup (letters, digits, _, - and .);
  • subscription;
  • build (acr or local);
  • registry (by default from an <registry>.azurecr.io image);
  • migrationTimeoutSeconds (1800) and revisionTimeoutSeconds (600).

az uses its own sign-in; Mayura reads no credentials. On Windows az is a .cmd script, which mayura deploy runs through cmd.exe with checked, quoted arguments.

See Deploy with mayura deploy. Apache-2.0.