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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@xpr/nestjs-slack-assistant

v2.0.0

Published

NestJS server implementation of the Slack Assistant

Readme

@xpr/nestjs-slack-assistant

This package export all decorators from @xpr/nestjs-slack package. See @xpr/nestjs-slack documentation for more details.

Usage

Installation

npm i @xpr/nestjs-slack-assistant

Transport

Minimal required configuration includes token and app token.

More information about slack tokens: https://api.slack.com/concepts/token-types

const token = process.env.SLACK_BOT_TOKEN as string;
const appToken = process.env.SLACK_APP_TOKEN as string;

const app = await NestFactory.createMicroservice(MyChatModule, {
  strategy: new SlackAssistant({
    slack: {
      token,
      appToken,
    },
  }),
});

await app.listen();

Controller

The package exports 3 decorators:

  • @ThreadStarted - triggered when a thread is started (slack docs)
  • @ThreadContextChanged - triggered when a thread context is changed (slack docs)
  • @UserMessage - triggered when a user sends a message in a thread (slack docs)

The only mandatory decorator is @UserMessage, but you can use the other two to handle thread context changes and thread started events.

@SlackController()
class ChatController {
  @ThreadStarted()
  async start(
    { say, setSuggestedPrompts, saveThreadContext }: ThreadStartedArgs,
  ) {
    try {
      await say("Hi, how can I help you?");
      await saveThreadContext();
      await setSuggestedPrompts({
        title: "Here are some suggested options:",
        prompts: [
          {
            title: "What is the weather like today?",
            message: "...the prompt to the LLM...",
          },
          {
            title: "Tell me a joke",
            message: "...the prompt to the LLM...",
          },
        ],
      });
    } catch (err) {
      this.logger.error("start failed", err);
    }
  }

  @ThreadContextChanged()
  async contextChanged({ saveThreadContext }: ThreadContextChangedArgs) {
    await saveThreadContext();
  }

  @UserMessage()
  async message({ message, say /*, client*/ }: UserMessageArgs) {
    // use the client to interact with slack
    // client.views.open()
    try {
      // client.views.update
      const response = await this.llmAgent.invoke(
        (message as { text: string })?.text ?? "",
      );
      await say(response);
    } catch (err) {
      this.logger.error("message failed", err);
    }
  }
}