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

@logtura/destination-slack

v0.2.11

Published

Logtura destination driver for Slack incoming-webhook posts.

Readme

@logtura/destination-slack

Logtura destination driver for Slack incoming-webhooks. Emits a Vector pipeline that coerces each matched event into Slack's expected { "text": "..." } body shape and POSTs it to the configured webhook URL.

npm install @logtura/destination-slack @logtura/core

Config

interface SlackConfig {
  webhookUrl: string;       // https://hooks.slack.com/services/T.../B.../...
  teamName: string | null;  // optional, label only
  channel: string | null;   // optional, label only
}

webhookUrl is a Slack Incoming Webhook URL. Get one at api.slack.com/messaging/webhooks: create or pick a Slack app in your workspace, enable Incoming Webhooks, click "Add New Webhook to Workspace", pick a channel. Slack returns a URL of the shape https://hooks.slack.com/services/T.../B.../....

teamName and channel are optional labels. The driver does not use them at runtime. They are useful if you want to display "which Slack workspace and channel does this sink post to?" in your own UI.

Usage

import { slackDriver } from "@logtura/destination-slack";

// Pass to generateBundle({ destinations: [slackDriver], ... }).
// In the sink, set destinationConfig to a SlackConfig.

What it emits

A pre-sink remap plus an http sink:

sink_<id>_format:
  type: remap
  inputs: [<upstream>]
  source: |-
    msg = string(.message) ?? ""
    if msg == "" { msg = "(empty .message) " + encode_json(.) }
    . = { "text": msg }

sink_<id>:
  type: http
  inputs: ["sink_<id>_format"]
  uri: "${SLACK_WEBHOOK_URL_<id>}"
  method: post
  encoding: { codec: json }
  framing: { method: newline_delimited }
  batch: { max_events: 1, timeout_secs: 5 }

The framing: newline_delimited plus max_events: 1 combo is load-bearing. Slack's incoming-webhook endpoint expects a top-level JSON OBJECT per request and 400s on a JSON ARRAY. Vector's codec: json defaults to wrapping a batch as an array, so each event has to be its own request.

The fallback if msg == "" { msg = "(empty .message) " + encode_json(.) } exists because Slack rejects { "text": "" } with no_text 400. Upstream normalizers should produce non-empty messages. This is the last line of defense.

License

Apache 2.0.