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

telelog-js

v0.1.1

Published

Envie logs e alertas para o Telegram em 60s (Node/TS)

Readme

telelog-js

Envie logs e alertas para o Telegram em 60 segundos (Node/TypeScript).

Instalação

npm i telelog-js

Uso mínimo

import { sendTelegram } from "telelog-js";
await sendTelegram("deploy ok ✅");

Winston

import winston from "winston";
import { telegramWinstonTransport } from "telelog-js/winston";

const logger = winston.createLogger({
  transports: [telegramWinstonTransport()],
});
logger.warn("atenção");

Pino

import pino from "pino";
import { createPinoTransport } from "telelog-js/pino";

const logger = pino({}, createPinoTransport());
logger.info("olá");

Variáveis de ambiente

  • TELEGRAM_BOT_TOKEN
  • TELEGRAM_CHAT_ID ou TELEGRAM_CHAT_IDS (separados por vírgula)
  • TELEGRAM_PARSE_MODE (opcional: MarkdownV2 ou HTML; padrão: texto puro)

CLI

telelog "mensagem"

Códigos de saída:

  • 0: sucesso
  • 1: falha de envio
  • 2: uso incorreto ou configuração ausente

Comportamento

  • Truncamento em 4096 caracteres com sufixo ....
  • Retries (3), timeout (5s), backoff exponencial base 500ms com jitter ±20%.
  • 429: respeita retry_after do Telegram.
  • MarkdownV2/HTML: escape automático quando TELEGRAM_PARSE_MODE definido.

Segurança

Nunca commitar .env. Use .env.example como referência e secrets no CI/CD.

Requisitos

  • Node >= 18.
  • ESM: use arquivos .mjs ou defina "type": "module" no package.json.
    • Em projetos CommonJS, utilize import dinâmico: import('telelog-js').then(m => m.sendTelegram(...)).

Variáveis de ambiente e .env

  • O pacote lê um arquivo .env do diretório atual (CWD), se existir.
  • Variáveis já definidas no ambiente têm precedência e não são sobrescritas pelo .env.
  • Necessárias:
    • TELEGRAM_BOT_TOKEN
    • TELEGRAM_CHAT_ID ou TELEGRAM_CHAT_IDS (múltiplos separados por vírgula)

Autor & Contato

  • GitHub: https://github.com/ZarabaDev
  • E-mail: [email protected]
  • Site: https://zarabatech.com.br