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

rbin-app-monitor

v1.0.8

Published

CLI para configurar projetos compatíveis com o RBIN App Monitor.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

rubensdeoliveirarubensdeoliveira

Keywords

rbinapp-monitorcypressgithub-actionsmonitoringe2e

Readme

rbin-app-monitor

CLI para preparar um projeto com Cypress para integração com o RBIN App Monitor.

O comando configura o contrato esperado pelo monitor: workflow workflow_dispatch, execução Cypress headless e artifact cypress-results com output.json.

Uso

npx rbin-app-monitor configure

Ou, após instalar globalmente:

rbin-app-monitor configure

Requisitos no projeto destino

  • Node.js 18.18 ou superior
  • Cypress já instalado ou configurado
  • package.json na raiz do projeto
  • repositório hospedado no GitHub

O que o comando faz

  • detecta Cypress no projeto atual
  • garante o script test:rbin-app-monitor sem alterar o script test
  • garante o script test:browser quando ele não existe
  • cria .github/workflows/cypress-e2e.yml
  • cria scripts/rbin-app-monitor/normalize-cypress-json.mjs
  • cria scripts/rbin-app-monitor/run-cypress-headless.mjs
  • configura o workflow para instalar e verificar o binário do Cypress
  • configura o workflow para gerar artifact cypress-results com output.json
  • configura o workflow para gerar artifact cypress-raw-output com output.raw.json
  • configura o passo final Notify RBIN App Monitor, que avisa o monitor quando o run termina (callback em /api/cypress/callback)

O workflow roda workflow_dispatch, usa uma URL remota quando configurada ou sobe a aplicação no CI, espera a URL responder e executa Cypress em modo headless.

URL monitorada

Para rodar contra uma URL publicada, configure a variável do repositório no GitHub:

CYPRESS_PRODUCTION_BASE_URL=https://sua-aplicacao.com

Caminho no GitHub:

Settings > Secrets and variables > Actions > Variables

Também é possível informar base_url manualmente ao disparar o workflow.

Se nenhuma URL remota for configurada, o workflow tenta subir a aplicação localmente com pnpm start, npm run start ou yarn start e usa http://127.0.0.1:3000.

Opções

rbin-app-monitor configure --dry-run

--dry-run mostra o que seria criado sem escrever arquivos.

Por padrão, o comando sobrescreve os arquivos de integração gerados pelo CLI.

Depois de configurar

No RBIN App Monitor:

  • cadastre o projeto com o repositório no formato owner/repo
  • configure a integração GitHub com um PAT capaz de disparar workflows e ler artifacts