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

@androwebdev/vibecoder-telegram

v1.0.21

Published

A CLI package that scaffolds a Telegram-based coding assistant into an existing Node.js project.

Readme

vibecoder-telegram

A CLI scaffolder that adds a Telegram-based coding assistant into an existing Node.js project.

Features

  • npx vibecoder-telegram init
  • npx vibecoder-telegram init my-project
  • Generates telegram/ folder with modular commands and utilities
  • Generates .env.example
  • Injects bot scripts into target package.json
  • Automatically installs required runtime dependencies
  • Includes error handling, timestamp logging, and VS Code file creation support

Installation

Use npx directly without installing globally:

npx vibecoder-telegram init

Or generate into a target folder:

npx vibecoder-telegram init my-project

Usage

Run the CLI in the target project directory:

cd existing-node-project
npx vibecoder-telegram init

If you want to scaffold into another path:

npx vibecoder-telegram init path/to/project

If you already installed an older scaffold and want to refresh Telegram files and scripts after upgrading the package:

npx vibecoder-telegram init --force

Or for a specific target:

npx vibecoder-telegram init path/to/project --force

Generated bot commands

  • /ping — test bot online
  • /cmd <shell command> — execute command and return stdout/stderr
  • /new <relative/file/path> — create a file recursively and open it in VS Code
  • /vibe [relative/file/path] — start a vibe coding session by creating/opening a file and launching the editor
  • /prompt <your Copilot prompt> — create a prompt file and open it in VS Code so GitHub Copilot can continue the coding flow
  • /copilot [--allow-all] <task or question> — run GitHub Copilot CLI directly from Telegram and return the result

Required environment

Copy .env.example to .env and set values:

TELEGRAM_BOT_TOKEN=your_bot_token
ALLOWED_CHAT_ID=123456789
OPEN_EDITOR_COMMAND=code
COPILOT_COMMAND=gh copilot
COPILOT_ALLOW_ALL=false

Set COPILOT_ALLOW_ALL=true if you want the bot to prepend /allow-all automatically on every /copilot request. You can also enable it per request by using /copilot --allow-all <task>.

Target package scripts

The initializer injects these scripts into the target package.json:

  • telegram:start
  • telegram:env

Notes

  • The generated bot uses polling via node-telegram-bot-api.
  • /cmd, /new, and /copilot commands are restricted to ALLOWED_CHAT_ID for security.
  • OPEN_EDITOR_COMMAND defaults to code for VS Code integration.
  • COPILOT_COMMAND defaults to gh copilot; make sure GitHub CLI and Copilot CLI are installed and authenticated before using /copilot.