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-bot-stub

v0.1.2

Published

Telegram bot project stub.

Downloads

11

Readme

telegram-bot-stub

Project stub for smart telegram bots based on telegram-bot-node.

Requirements

  • nodejs >= 0.10
  • npm >= 1.2.0

Quick start

git clone https://github.com/zloylos/telegram-bot-stub.git <YOUR_PROJECT_NAME>
cd <YOUR_PROJECT_NAME>
rm -rf .git && git init
npm install 
npm start

How it works

Project structure: lib folder

configs/        Token and other info.
lang/           Localization.
lib/plugins     Contains bot plugins
lib/handlers    Common handlers for reuse. If you have command /weather, and react on text with some results.
lib/providers   Modules for load data.

Messages

For add new handler, you need create plugin into plugin-folder. More information about plugins you can find here.

MongoDB

For using DB you need to call method myBot.setUserCollection(<MongoDBCollection>). index.js file will looks like this:

var MongoClient = require('mongodb').MongoClient;
var path = require('path'),
var Bot = require('telegram-bot-node').Bot;
var config = require('./configs/config');

var myBot = new Bot(config.TELEGRAM_TOKEN, {
    // Setup polling way
    polling: true,
    plugins: path.resolve(__dirname, './lib/plugins')
});

MongoClient.connect(config.MONGO_URL, function(err, db) {
    if (err) {throw err;}

    console.log("Connected correctly to MongoDB server");

    myBot.setUserCollection(db.collection('users');
    myBot.on('message', function (msg) {
        myBot.handle(msg);
    });

    console.log("App runned");
});

Users

By default all handlers get user object in info variable. How can you use it? If user sent location before and ask weather without parameters, you can answer with his old location.

var MESSAGE_TYPES = require('telegram-bot-node').MESSAGE_TYPES;
var weatherHandler = require('../handler/weather');
var request = require('superagent');
var vow = require('vow');
var WEATHER_URL = 'http://api.openweathermap.org/data/2.5/weather';
var K = 273.15;

module.exports = {
  type: MESSAGE_TYPES.COMMAND,
  test: function (info) {
    return info.data.command === 'weather';
  },
  handler: function (info, bot) {
    var user = info.user;
    var query = !info.data.params && user && user.location ? 
      {
        lat: user.location.latitude, 
        lon: user.location.longitude
      } : 
      {q: info.data.params};
    
    return weatherHandler.get(query);
  }
};

Now we can use /weather command without params.