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

@web-standards-ru/calendar-bot

v1.0.4

Published

Module for post events from web-standards-ru/calendar

Downloads

8

Readme

calendar-bot Telegram bot for web-standards-ru-calendar

Instaling

npm i -S @web-standards-ru/calendar-bot

Usage

In script

const moment = require('moment');

const sendToChannel = require('@web-standards-ru/calendar-bot/tlgrm.js');
const WSEvent = require('@web-standards-ru/calendar-bot/wsevent.js');

sendToChannel(WSEvent.fromYaml(`name: Яндекс Субботник
date: 10.12.2016
city: Москва
link: https://events.yandex.ru/events/yasubbotnik/10-dec-2016/
`), 'token', 'channel', 'proxy', (event) => {
    //this is a default value when this function is not set
    moment.locale('ru');
    return `[${event.name}](${event.link})\n${event.city}, ${moment(event.start).utc().format('DD MMMM YYYY')}`);
})
    .then((res) => {
        const { status, body } = res;
        //check status == 200
    })
    .catch((err) => {
        console.warn(err);
    });

As cli

node . --token=111 --channel=@wsdc_test --proxy=socks://127.0.0.1:9050 events/2016-11-24-moscowjs1.yml events/2016-11-24-moscowjs2.yml

Without install

npx github:web-standards-ru/calendar-bot --token=111 --channel=@wsdc_test --proxy=socks://127.0.0.1:9050 events/2016-11-24-moscowjs1.yml events/2016-11-24-moscowjs2.yml

Args:

  • token - bots token
  • channel - channel name
  • proxy - url for proxy (for example Telegram blocker in you country), not necessarily
  • all last args - paths for yaml event files

Returning code:

  • 0 - successed
  • 1 - sending exception
  • 2 - not 200 http response code
  • 255 - not set files

Tests

For test run

TOKEN='{bot_token}' CHANNEL='@{channel_name}' PROXY='{proxy_url}' npm run test
  • TOKEN - token telegrams bost
  • CHANNEL - channel name, for e.g. @test_channel (telegram bot must be a an administrator)
  • PROXY - proxy url, for e.g. socks://127.0.0.1:9050 for a local tor daemon

Versions

  • 0.0.1
  • 0.0.2:
    • fix date to utc
  • 0.0.3:
    • add deleteMessage()
  • 0.0.4:
    • add standalone script
  • 1.0.0:
    • add cli
  • 1.0.1:
    • cli as default
  • 1.0.2:
    • upd README
  • 1.0.3:
    • add bin in package
  • 1.0.4:
    • multi-send files