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

@kedoska/exp2slack

v0.1.4

Published

Send errors to slack

Downloads

5

Readme

exp2slack

You can use this to report errors to Slack from your node application, as an ExpressJs middleware or standalone library.

Get Your Slack Web Hook Url

  1. set up a new application in slack
  2. create a new Incoming Webhooks and get your SLACK_WEBHOOK_URL
  3. npm i @kedoska/exp2slack --save or yarn add @kedoska/exp2slack

Use it as express middleware

See the example and make sure you are initializing this middleware AFTER all your app setup/routes. Also consider that when this is a middleware it will:

  1. report the error to slack (wait for slack to reply)
  2. call next passing the original error in the express pipeline. This will may slowdown your application (if it is firing a lot of errors).
const express = require('express') // <-- Step 1
const exp2slack = require('@kedoska/exp2slack')
const app = express()

const url = 'https://hooks.slack.com/services/XXXXXXXXX/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'

app.get('/', (req, res) => {
  const runTimeError = foo + bar  // <-- Step 3 ( foo not defined)
})

app.use((exp2slack(url))) // <-- Step 2

app.listen(8080)

More details about Express Error Handling available here

Now without express

Once you have initialized the IncomingWebhook with your url you can manually push an error to slack by calling the notify function. Here the example without express.

After passing the url to the configure method, you can notify any Error.

const { configure, notify } = require('@kedoska/exp2slack') // <-- Step 1
const url = 'https://hooks.slack.com/services/XXXXXXXXX/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'

configure(url) // <-- Step 2

const initApplication = () => {
  try {
    throw new Error('')
  } catch (err) {
    notify(err) // <-- Step 3
  }
}

initApplication()

Dependencies

  1. error-stack-parser
  2. node-slack-sdk (@slack/client)

Extra code and fancy If/s

:warning: I'm adding some extra if to the original output of error-stack-parser. Mainly to cut some paths and try to get a nice format in slack.