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

botkit-zulip

v0.2.0

Published

BotKit Zulip connector

Downloads

4

Readme

BotKit connector for Zulip

In your bot's directory, run:

npm install --save botkit-zulip

Creating a BotKit controller

In the bot JavaScript, to create a Botkit controller use the following lines.

var Botkit = require('botkit');
var controller = require('botkit-zulip')(Botkit, {});

Setup

On your Zulip setting page, create a Generic bot account. Note its email and API key. The bot will only listen to streams it is subscribed to.

When controller.spawn() is called it uses the following environment variables are used to configure the bot.

  • [email protected] (required)
  • BOTKIT_ZULIP_API_KEY=<Bot api key> (required)
  • BOTKIT_ZULIP_SITE=https://chat.zulip.org (optional, defaults to http://localhost:9991)

Alternatively, you can explicitly specify the configuration programatically, like so:

controller.spawn({
  zulip: {
    username: '[email protected]',
    apiKey: <bot api key>,
    realm: 'https://chat.zulip.org'
  }
});

BotKit Studio integration

To use BotKit studio, obtain a BotKit studio token. See the BotKit Getting Started Guide on how to do this.

Once you have a token, you can set the following environment variable.

  • BOTKIT_STUDIO_TOKEN=<BotKit Studio Token> (optional)

Running the test bot

The testbot is intended for quickly trying out the connector during development. It is not intended as a template for a production bot. It would be preferred to follow the official Botkit Get Started guide and then making the modifications described above in Creating a BotKit controller.

To use the bot, create a .env file in the project directory with the following contents:

BOTKIT_STUDIO_TOKEN=<BotKit Studio token, optional>
[email protected]
BOTKIT_ZULIP_API_KEY=<bot api key>
BOTKIT_ZULIP_SITE=http://localhost:9991

and then run npm run testbot

If you have BOTKIT_STUDIO_TOKEN set, you will also be able to try the starter BotKit Studio scripts that are available to your account. (e.g. hello, goodbye, tutorial, etc.)