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

@shpe-utdallas/sync-dotenv-slack

v0.1.0

Published

Keep .env in sync with teammates on Slack

Downloads

2

Readme

sync-dotenv-slack

Keep .env in sync with teammates on Slack

sync-dotenv-slack-demo

Travis (.org) Coverage Status

While having a .env.example file committed to source control might help in letting teammates know that certain environmental variables are required to get up and running with a project, getting them the values can be a pain. Even worse, alerting them when any of those values (or variables) changes can be a drag.

sync-dotenv-slack automates the process of keeping your teammates in the loop when .env changes (locally) by securely notifying them on Slack.

Features

  • Automatic synchronization when env (key/value) changes
  • Securely upload env contents as a file snippet to Slack channel
  • Private/Public Slack channel support
  • Exclude/Include specific env (values) to upload

Table of contents

Prerequisites

Installation

$ npm install -D sync-dotenv-slack

Setup

  • Create a Slack app (with required permissions) for your workspace. Follow this guide
  • Add Slack app tokens to your project .env
    ENVBOT_SLACK_BOT_TOKEN=xoxb-******-******-******
    ENVBOT_SLACK_USER_TOKEN=xoxp-*****-*****-*****-*****

Usage

To use this tool, an envbot object needs to be added to your project's package.json like so. See the config section for more info

// package.json
  "scripts": {
    ...
    "sync-dotenv-slack": "envbot"
  },
  "envbot": {
    "channel": "general",
    "include": ["*", "!SECRET"]
  }

You can then run $ npm run sync-dotenv-slack

or

Automagically sync before every push using husky or similar tool (recommended)

{
    ...
+   "husky": {
+    "hooks": {
+      "pre-push": "npm run sync-dotenv-slack"
+     }
+   }
}

Config

You can configure the envbot object with the following options in package.json

channel

Type: string

Slack channel (name) to post/upload env to.

include

Type: [string]

An array of environment variable(s) to include/exclude their values when posting to Slack.

Using the include option
# include all env values
["*"]

# include all env values but AWS_SECRET
["!AWS_SECRET"]

# ignore all env values but DB_NAME
["!TOKEN", "DB_NAME"] 

# ignore all env values but DB_NAME & DB_HOST
["DB_NAME", "DB_HOST"]

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

License

This project is licensed under MIT

Contributors