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

gatsby-source-slack

v0.5.4

Published

Source plugin to fetch channels from Slack into Gatsby

Downloads

11

Readme

gatsby-source-slack

Use your Slack API token to download your channels and users into Gatsby's GraphQL data layer!

Please note: This plugin was made out of a specific necessity, so it doesn't cover all of Slack's API capabilities, focusing only on channels and users. If you want to add extra functionalities, feel free to create a PR and contribute :smile:

See this plugin in action here

Table of content

Basic usage

yarn add gatsby-source-slack
# or
npm i gatsby-source-slack --save
// in your gatsby-config.js
module.exports = {
  // ...
  plugins: [
    {
      resolve: 'gatsby-source-slack',
      options: {
        // Avoid including your token directly in your file.
        // Instead, opt for adding them to .env files for extra
        // security ;)
        token: 'xoxp-asdkl1posdapo12-asjsdi12idsaioo',
      },
    },
  ],
  // ...
};

Go through http://localhost:8000/___graphql after running gatsby develop to understand the created data and create a new query and checking available collections and fields by typing CTRL + SPACE.

Options

| Options | Type | Default | Description | | ----------------- | ---------------- | ------- | ------------------------------------------------------------------------------------------- | | key | string | | [required] Your API key | | channelsToFetch | array of strings | [] | The IDs of channels you'd like to fetch | | normalizeMessages | boolean | false | Wether the plugin should format messages' text to include the referenced users, links, etc. |

Using .env variables to hide your key

If you don't want to attach your API key to the repo, you can easily store it in .env files by doing the following:

// In your .env file
SLACK_TOKEN = 'xoxp-asdkl1posdapo12-asjsdi12idsaioo';

// In your gatsby-config.js file
require('dotenv').config({
  path: `.env.${process.env.NODE_ENV}`,
});

module.exports = {
  // ...
  plugins: [
    {
      resolve: 'gatsby-source-slack',
      options: {
        token: process.env.SLACK_TOKEN,
        // ...
      },
    },
  ],
  // ...
};

This example is based off Gatsby Docs' implementation.

TODO

  • Pass down the whole message objects into normalizedMessages;
  • Better documentation on normalizeMEssages;
  • Tutorial on how to set-up a Slack clone - maybe open source the one I've made;
  • Live example of this working

License

I'm not very literate on licensing, so I just went with MIT, if you have any considerations just let me know! Oh, and, of course, feel free to contribute to this plugin, even bug reports are welcome!