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 🙏

© 2025 – Pkg Stats / Ryan Hefner

telegram-bot-typescript

v0.0.3

Published

Auto-generated types for the Telegram bot API. Produced by regularly parsing documentation and published as an NPM package.

Readme

Telegram Bot API in Typescript

Auto-generated types for the Telegram bot API. Produced by regularly parsing documentation and published as an NPM package.

Why?

Telegram provides a rich API for implementing bots. While Telegram publishes detailed documentation, they do not provide machine-readable schemas. This has resulted in most libraries being unable to provide full type coverage for their methods.

This library attempts to change that.

How?

A codegen script is regularly executed, which parses the HTML documentation and outputs a TypeScript definition file.

This process is somewhat brittle, but the output is high quality, including:

  • Every type definition
  • Options for every exposed method
  • JSDoc annonations for everything
  • Return types for every method

Can I build bots with this?

If you're comfortable implementing your own network layer, yes. However, this is primarily intended to be consumed by other libraries which would provide concrete methods for calling the API directly.

Correctness of Types

It seems like the docs are written by hand because of small inconsistencies. This requires...

  1. Fault-tolerant code
  2. Hard-coded exceptions to rules
  3. Ad-hoc string matching and regular expressions

This is where the brittleness comes from: changes in language to the docs can cause types to be incorrect. If you spot a case of a type being incorrect, please open an issue.

Conventions

Types

Type names are kept verbatim from the documentation, and exported as interfaces. If a type is used to refer to other types, a type alias union is used.

Methods

For each method there are two types exported. For input, the format is [methodName]Options. For the return type, the format is [methodName]Result

Future Work

Keeping up to date with documentation changes, fixing errors in output, and evolving the JSDoc annotation quality.

I'm looking to setup GitHub Actions CI for:

  • Generating types on a recurring basis, and opening PRs if a change is detected.
  • Creating a new release when such a PR is merged

Contributions welcome for all of the above!

License

GPLv3