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

liqueur

v1.2.0

Published

A rich-featured and flexible command framework for building WhatsApp bot with baileys inspired by @sapphire framework.

Downloads

13

Readme

liqueur

A rich-featured and flexible command framework to develop WhatsApp bot with Baileys inspired by @sapphire framework.

GitHub npm

Installation

npm i liqueur

Usage

The usage is similar to @sapphire/framework, you can open our coming soon example bot to get started.

Listening to Baileys' socket

Because Baileys' event emitter is kinda different (not a pure EventEmitter), you can use the following options to listen to it:

@ApplyOptions<ListenerOptions>({
    event: "connection.update", // Change the event name
    emitter: "baileysEmitter" // Specify the emitter (must be "baileysEmitter" !!)
})

While doing so will make the listener listens to the Baileys' event emitter. If you didn't specify the emitter name, it will listens to FrameworkClient internal events as defined here

Handle credentials nor connection update

We didn't handle the creds.update nor connection.update event by default. To make the bot working, please handle it according to your respective auth's state handler.

For example, using useMultiFileAuthState:

import { container } from "@sapphire/pieces";

@ApplyOptions<ListenerOptions>({
    event: "creds.update",
    emitter: "baileysEmitter"
})
export class CredsUpdate extends Listener {
    public async run(): Promise<any> {
        await container.authState?.saveCreds();
        this.container.client.logger.info("Credentials has been updated.");
    }
}

...in your main file:

import { container } from "@sapphire/pieces";
import { useMultiFileAuthState, makeWASocket } from "@whiskeysockets/baileys";

const loggerOptions = createLogger({
    name: "WhatsApp-bot",
    debug: mode === "dev"
});

const client = new FrameworkClient({
    baseUserDirectory: "dist",
    fetchPrefix: () => Promise.resolve(prefix),
    makeWASocket: () => {
        container.authState = useMultiFileAuthState("auth_state");
        return makeWASocket({
            auth: {
                // Pass the auth strategy here
                creds: container.authState.state.creds,
                // @ts-expect-error-next-line
                keys: makeCacheableSignalKeyStore(container.authState.state.keys, logger)
            },
            printQRInTerminal: true
        })
    },
    logger
});

Don't forget to handle the reconnection:

import { Listener, ListenerOptions } from "liqueur";
import { BaileysEventMap, DisconnectReason, useMultiFileAuthState } from "@whiskeysockets/baileys";
import { Boom } from "@hapi/boom";
import { cast } from "@sapphire/utilities";
import { ApplyOptions } from "@nezuchan/decorators";

@ApplyOptions<ListenerOptions>({
    event: "connection.update",
    emitter: "baileysEmitter"
})
export class ConnectionUpdate extends Listener {
    public async run({ lastDisconnect, connection }: BaileysEventMap["connection.update"]): Promise<any> {
        const shouldReconnect = cast<Boom | undefined>(lastDisconnect)?.output?.statusCode !== DisconnectReason.loggedOut;
        if (connection === "close") {
            this.container.client.logger.warn(
                `Connection closed due to ${lastDisconnect?.error?.message ?? "unknown reason"
                }, reconnecting ${shouldReconnect}`
            );
            if (shouldReconnect) {
                await this.container.client.login();
            }
        } else if (connection === "open") {
            this.container.client.logger.info("Opened connection.");
        }
    }
}

Credits

Thanks to @sapphire developers for giving inspiration and concepts. This framework 100% based on their packages and designs.