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 🙏

© 2025 – Pkg Stats / Ryan Hefner

landingbot

v1.1.0

Published

A bot to help drive engagement for any landing page.

Downloads

18

Readme

npm version Dependency Status Code Climate

Demo

Visit my personal landing page to take it for a test drive

Installation

npm i landingbot -S

Usage

Landingbot can be used with no additional options, like below.

const Landingbot = require('landingbot');
let landingbot = new Landingbot();

However, that does not provide much functionality. You probably want to supply options like this..

const Landingbot = require('landingbot');
let landingbot = new Landingbot({
  name: 'Cambot',
  page: 'Cam\'s site',
  owner: 'Cam'
});

Additionally a slack_hook can be specified in the options, to allow for realtime correspondece via Slack. You must create an incoming webhook with Slack.

Note: This is only step one of two to enable back and forth communication from Slack to landingbot and vice versa

Want to use Custom Expressions?

Well you can do that too! The second arguement of the constructor accepts an array of objects. You can do that like this...

const Landingbot = require('landingbot');
const customExpressions = [
  {
    regex: /Is\ this\ some\ question/ig,
    question: 'Is this some question?',
    response: 'Landingbot's reply to the question'
  }
];
let landingbot = new Landingbot({
  name: 'Cambot',
  page: 'Cam\'s site',
  owner: 'Cam'
}, customExpressions);

Examples

Using landingbot on the server-side with socket.io and incorporating Slack. This example assumes your client is listening for a msg event as well as emitting one for every new message.

Have a look at this for what it may look like.

Remember how I mentioned there were two steps to enable back and forth comms within Slack? Well in this configuration the next step is as follows.. First create an outgoing webhook with Slack. Then you need your server to handle a post to whatever hook url you specified.

Take a look here for a simple example.

You may notice we are parsing for an id, that's because in the current implementation we need to prefix every message with the user's socket id. Which is provided in all their messages via an attachment.

Stay tuned for an example of client-side usage example