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

@loskir/grammy-markup

v1.1.0

Published

Markup plugin for grammY

Downloads

22

Readme

Markup plugin for grammY

This plugin provides telegraf-like keyboard and inline keyboard builders.

Motivation

The official plugin provides an imperative API, which I don't really like. This plugin, on the other hand, provides declarative helper functions inspired by telegraf.

See the comparison:

new InlineKeyboard([
  [IButton.text("Get random music", "random")],
  [IButton.switchInline("Send music to friends")],
])

vs

new InlineKeyboard()
  .text("Get random music", "random").row()
  .switchInline("Send music to friends")

The declarative approach is especially useful when you want to represent dynamic data in the menu (for example, obtained from the database):

const inlineKeyboard = new InlineKeyboard(items.map(
  (item) => [IButton.text(item.name, item.id)]
))

vs

const inlineKeyboard = new InlineKeyboard()
for (const item of items) {
  inlineKeyboard.text(item.name, item.id).row()
}

Also it's easy to use all sorts of array utilities with declarative builder, like chunk:

const inlineKeyboard = new InlineKeyboard(chunk(
  items.map((item) => IButton.text(item.name, item.id))
  3,
))

Installation

Yarn

yarn add @loskir/grammy-markup

NPM

npm i --save @loskir/grammy-markup

Usage

Deno

import {
    IButton,
    Button,
} from "https://github.com/Loskir/grammy-markup/raw/main/src/index.ts"

Typescript

import {
    IButton,
    Button,
} from "@loskir/grammy-markup"

Javascript

const {
    IButton,
    Button,
} = require("@loskir/grammy-markup")

Examples

IButton

const inlineKeyboard = new InlineKeyboard([
    [IButton.text('text', 'callback_data')],
    [IButton.url('text', 'https://grammy.dev')],
    [IButton.webApp('text', 'https://grammy.dev?webApp')],
    [IButton.login('text', 'https://grammy.dev?login')],
    [
        IButton.switchInline('text', 'query'),
        IButton.switchInlineCurrent('text', 'query'),
    ],
    [IButton.game('text')],
    [IButton.pay('text')],
])
// ctx.reply('inline keyboard', {reply_markup: inlineKeyboard})

Button

const keyboard = new Keyboard([
    [Button.text('text')],
    [Button.requestContact('text')],
    [Button.requestLocation('text')],
    [Button.requestPoll('text', 'quiz')],
    [Button.webApp('text', 'https://grammy.dev?webApp')],
])
// ctx.reply('keyboard', {reply_markup: keyboard})