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

@amityco/amityeko-bot-messenger

v2.1.0

Published

A simple github action to send a message to AmityEko's app

Downloads

14

Readme

AmityEko Bot Messenger

What is it?

This is a:

Who is it for?

For engineers whose company is using AmityEko, a way to automate messages of Github workflows and such.

Notes on usage

Although you may find useful at first to send lots of messages for integration, be aware that CI usually runs very often and you may end up flooding your group with messages. When doing so, you may drag the interest of the groups users out of the group: they may end up not reading the messages, because there are too many messages to read.

Be a responsible human being and don't spam your peers :)

How to use it?

Github Action

In your workflow, add:

  - uses: AmityCo/amityeko-bot-messenger@v1
    with:
      accessToken: {{ secrets.AMITYEKO_TOKEN }}
      groupId: {{ secrets.AMITYEKO_GROUP_ID }}
      threadId: {{ secrets.AMITYEKO_THREAD_ID }}
      content: |
        Hello world!
        This is a multi-line message :)

You can also send an image (even a gif) with:

  - uses: AmityCo/amityeko-bot-messenger@v1
    with:
      accessToken: {{ secrets.AMITYEKO_TOKEN }}
      groupId: {{ secrets.AMITYEKO_GROUP_ID }}
      threadId: {{ secrets.AMITYEKO_THREAD_ID }}
      type: image
      content: https://cataas.com/cat/gif

NPM package

  1. npm i -D @amityco/amityeko-bot-messenger
  2. import sendMessage from '@amityco/amityeko-bot-messenger'

The signature function is:

function(
  serverEndpoint: string,
  accessToken: string,
  groupId: string,
  threadId: string,
  type: 'text' | 'image',
  content: string,
): Promise<void>

Command line usage

  1. npm i -g @amityco/amityeko-bot-messenger
  2. aem text "hello world" or aem image https://cataas.com/cat/gif

Configuration

You can provide informations about server endpoint, access token, group and thread ids in few different ways.

  1. In a JSON file $HOME/.aemrc:
{
  "serverEndpoint": "",
  "accessToken": "",
  "groupId": "",
  "threadId": ""
}
  1. As environment variables:
AMITYEKO_SERVER_ENDPOINT= AMITYEKO_ACCESS_TOKEN= AMITYEKO_GROUP_ID= AMITYEKO_THREAD_ID= aem text "hello world"
  1. As command arguments:
aem text "hello world" --endpoint= --token= --gid= --pid=

Where can I find the necessary variables?

Access Token

The bot account must be created from the AmityEko admin panel, therefore you must either have access to it or ask an admin to create a bot for you. If you need more informations, ask the AmityEko staff for details.

Group ID, Thread ID

When connected to the AmityEko app, you can easily find this information from the url. See the screenshot below for finding the correct values: