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

v1.2.0

Published

Render as a mayura deploy target: a Blueprint with a web service, a background worker and PostgreSQL.

Downloads

197

Readme

@mayurajs/deploy-render

Render as a mayura deploy target: a Blueprint with the server as a web service, a background worker and PostgreSQL, released with the Render CLI.

npm install --save-dev @mayurajs/deploy-render
mayura deploy init --target render --apply   # writes render.yaml and deploy/render/Dockerfile; commit and push them
# Once: in the dashboard, New > Blueprint from the repository, and enter the secrets it asks for. Then set
# targets.render.serverServiceId and workerServiceId (srv-…) in mayura.deploy.json.
mayura deploy --target render                # prints the plan and its digest
mayura deploy --target render --apply --confirm <digest>
  • render.yaml describes:
    • a web service (serve, with a /readyz health check);
    • a background worker;
    • a PostgreSQL database, given to both as DATABASE_URL.
  • Both services build from deploy/render/Dockerfile, an image without an entry point, so their full start and pre-deploy commands run as written.
  • Both services migrate storage before they go live. Migrations take a lock, so whichever runs first does the work, and a failed migration fails the deploy.
  • Each variable named in env in mayura.deploy.json is declared with sync: false. Render asks for its value when you create the Blueprint, so values never reach the repository.
  • Render deploys from your repository, so push before releasing.
  • A release:
    1. validates the Blueprint with render blueprints validate;
    2. runs render deploys create <id> --wait for the server, then the worker, stopping at the first failure.
  • autoDeploy is off by default, so releases go through mayura deploy. Set commit or checksPass to let Render deploy on its own.
  • Settings in mayura.deploy.json under targets.render:
    • region (oregon), plan (starter; pre-deploy commands need a paid instance type) and databasePlan (basic-256mb);
    • autoDeploy;
    • serverServiceId and workerServiceId.
  • The Render CLI uses its own login (render login), or RENDER_API_KEY in CI. Mayura reads neither.

See Deploy with mayura deploy. Apache-2.0.