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

@thzero/library_server_messaging_slack

v0.19.1

Published

![GitHub package.json version](https://img.shields.io/github/package-json/v/thzero/library_server_messaging_slack) ![David](https://img.shields.io/david/thzero/library_server_messaging_slack) [![License: MIT](https://img.shields.io/badge/License-MIT-yello

Readme

GitHub package.json version David License: MIT

library_server_messaging_slack

Posts messages to Slack from @thzero/library_server, using @slack/web-api.

Intended for operational notices — a deploy finished, a job failed, a threshold was crossed. It is not a chat integration and does not receive anything from Slack.

Requirements

NodeJs

NodeJs version 22+

Slack

A Slack app with a bot token:

  • Create an app at api.slack.com/apps
  • Under OAuth & Permissions, add the chat:write bot token scope
  • Install the app to the workspace and copy the Bot User OAuth Token (xoxb-…)
  • Invite the bot to each channel you intend to post to — chat.postMessage fails with not_in_channel otherwise

Installation

NPM

npm install @thzero/library_server_messaging_slack

Peer dependencies

  • @thzero/library_common
  • @thzero/library_common_service
  • @thzero/library_server

What it provides

index.js — default export MessagingService, extending Service.

| Method | Purpose | |---|---| | init(injector) | Reads the token from config and builds the WebClient. A failure here is logged, not thrown — the service stays constructed but unusable. | | message(correlationId, channel, message) | Posts message to channel via chat.postMessage. Returns a success response, or an error response carrying the correlationId when Slack rejects it. |

message never throws. A Slack outage produces a failed response and a logged exception rather than taking down the caller.

Configuration

{
    "app": {
        "messaging": {
            "slack": {
                "token": "xoxb-<bot user oauth token>"
            }
        }
    }
}

Keep the token out of source control — supply it from an environment variable through config/custom-environment-variables.json, the same way the database connection is handled.

Wiring it up

Register it with the injector from _initServices in your BootMain derived class, or from a boot plugin's initServices, then resolve it where you need it:

const serviceMessaging = injector.getService(AppConstants.InjectorKeys.SERVICE_MESSAGING_SLACK);
await serviceMessaging.message(correlationId, '#ops', `Deploy ${version} completed.`);

channel accepts either a channel name (#ops) or a channel ID (C0123456789). An ID is more robust — a renamed channel keeps its ID.

Development

npm run lint       # eslint .
npm run lint:fix   # eslint . --fix
npm test           # node --test "test/*.test.js"