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

@weblabllc/messengers

v0.3.1

Published

Framework-free messenger delivery channels behind one interface: Telegram, Viber, TurboSMS, eSputnik

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

risklightrisklight

Keywords

telegramvibersmsturbosmsesputniknotificationsmessengertypescript

Readme

@weblabllc/messengers

npm ci license

Framework-free delivery channels behind one NotificationChannel interface: Telegram Bot API, Viber, TurboSMS, eSputnik. No framework imports, no storage — pure clients over fetch.

Install

npm install @weblabllc/messengers

Enable any combination

import { ChannelRegistry } from '@weblabllc/messengers/registry'

const channels = await ChannelRegistry.create({ channels: ['telegram', 'esputnik'] })
await channels.get('telegram').send(
  { to: chatId, text: 'Замовлення ORD-1 оплачено' },
  { botToken: process.env.TG_TOKEN },
)

Or import one channel: import { TelegramChannel } from '@weblabllc/messengers/telegram'.

eSputnik

EsputnikChannel.send fires a platform event (eventTypeKey from config, keyValue = recipient) that triggers the scenario configured in eSputnik. The lower-level EsputnikClient also exposes upsertContacts with dedupeOn.

import { EsputnikClient } from '@weblabllc/messengers/esputnik'

const client = new EsputnikClient({ apiKey: '...', eventType: 'orderPaid' })
await client.upsertContacts([{ channels: [{ type: 'email', value: '[email protected]' }] }])

TurboSMS: SMS and hybrid Viber

TurboSmsChannel sends SMS by default. Add viberSender (a sender name activated in your TurboSMS account) and the same request goes out as Viber Business Message first, falling back to SMS after hybridTtlSeconds (default 60, clamped to TurboSMS's 30–86400 range; sent as viber.ttl + sms.hybrid_ttl). Viber messages are marked transactional unless viberTransactional: false; transactional texts to Ukrainian numbers must match templates pre-registered with TurboSMS.

import { TurboSmsChannel } from '@weblabllc/messengers/turbosms'

await new TurboSmsChannel().send(
  { to: '380671234567', text: 'Замовлення ORD-1 оплачено' },
  { apiKey: process.env.TURBOSMS_KEY, sender: 'Shop', viberSender: 'Shop' },
)

ViberChannel is the chatbot API (chatapi.viber.com); since 2024 bots are issued to businesses on application and billed monthly, so for transactional delivery to phone numbers the hybrid TurboSMS route is the practical one.

Errors and timeouts

Every channel posts with a 10 s AbortSignal.timeout; a non-JSON reply (a proxy's 502 page) comes back as { ok: false, detail: '<status>: <body>' } instead of throwing. TurboSMS codes 800–803 all count as sent.

Test

npm test