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

eslint-plugin-undocumented-env

v1.0.0

Published

eslint plugin to detect undocumented environment variables

Downloads

140

Readme

eslint-plugin-undocumented-env

eslint plugin to detect use of undocumented environment variables

This looks for usage of process.env.VARIABLE_NAME in your code, and checks that the environment variable is mentioned in your README file.

Usage

Add undocumented-env to the plugins section of your ESLint configuration file. You can omit the eslint-plugin- prefix:

plugins:
  - undocumented-env

Then configure the plugin under the rules section.

rules:
  - undocumented-env/no-undocumented: error

Options

By default undocumented-env will look for references to environment variables in the first README.md file it finds while traversing up the file tree.

To use a filename for documentation other than README.md then specify it as a readme option in your eslint config:

rules:
  - undocumented-env/no-undocumented:
    - error
    - readme: configuration.md

Caveats

This plugin will only detect variables accessed directly via process.env.VARIABLE. It will not detect any dynamic or programmatic references to process.env.

This plugin won't detect bad documentation, only completely absent documentation. You should still document your code.