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 🙏

© 2024 – Pkg Stats / Ryan Hefner

telegram-interface

v0.1.8

Published

TypeScript Interface for Telegram Bot API

Downloads

13

Readme

telegram-interface

An NPM package for interfacing with the Telegram Bot API TypeScript Support Available

!! Work in Progress

This is the very first npm library I've made and it's still in the early stages so not all methods on the Telegram Bot API are available. I've been re-using this codebase a lot so its about time I made it a package instead of copy-pasting what I need for every new project.

Full documentation coming soon.

Usage

There are two main ways to use this library: 1) Via the Wrapper Class or 2) Via the Functions

Wrapper Class

import { Telegram } from 'telegram-interface'

var tele = new Telegram(bot_key)
tele.parse_mode = 'HTML' // 'HTML' is the default. Can also use 'MarkdownV2'.

tele.sendMessage(chat_id, msg)
  .then((res) => console.log(res.data))
  .catch((err) => console.log(err))

Functions

import { sendMessage, genInlineButtons } from 'telegram-interface'
var btns = genInlineButtons([['1st row']['2nd row']], [[callback1], [callback2]])

sendMessage(botkey, chatId, text)
  .then(...)
  .catch(...)
sendMessage(bot_key, chat_id, text, btns, {parse_mode: 'MarkdownV2'})
  .then(...)
  .catch(...)

Notes for myself

Yes, I know this is a public-facing repo.

Workflow

Edits can be done normally and committed locally normally. If you're intending to publish to npm, don't push to remote just yet.

Also, I'm not quite sure why I committed the lib folder but it is what it is. I'll prob take it out in the future.

To publish to NPM, you have to have a clean git working directory. Do not build first. The following commands should do it.

Mark the current git HEAD as a new version. patch is used here for small changes, minor for new features/functionality, major for overhauls npm version patch -m <COMMIT_MESSAGE>

Login to NPM npm login

Publish to NPM npm publish

Push new commits to GitHub git push

Todos

  • [ ] Why is the lib folder on GitHub? Take it out.
  • [ ] Workflow should be branch -> commits -> PR -> Merge -> Pull master to version and npm publish and push back to master
  • [ ] Why pull master when you can just github actions to publish to npm?