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

document-env-vars

v2.1.0

Published

A webpack loader for making sure your README.md documents all the environment variables your code uses

Downloads

3

Readme

document-env-vars

A webpack loader for making sure your README.md documents all the environment variables your code uses.

This loader allows Webpack to automatically warn you code that you apply this loader to extracts an enviroment variable out of process.env or by using env.get() that is not mentioned anywhere in your README.md, which is usually a sign that your PR, or even your codebase, is not properly documented yet, while making it trivial to figure out which env var you haven't mentioned so you can immediately add it.

Install with npm

Installation is the same as for any other npm-managed package

$> npm install document-env-vars --save-dev

If you use a different manager with the npm registry (such as yarn) please look up the equivalent syntax for this instruction for your tool of choice.

Use as any other loader in your Webpack config

Use this webpack loader the same way you would any other loader. As an example:

  ...
  module: {
    loaders: [
      {
        test: /\.jsx?$/,
        loaders: [
          'babel-loader',
          'eslint-loader',
          'document-env-vars'
        ],
        exclude: /node_modules/
      },
      ...
    ]
  },
  ...

Remember that loaders work LIFO (last in, first out) so the last loader gets triggered first. This loader does not modify any files, so the order should not matter, but running it first by placing it at the end of your loader list means that it triggers on your code, not on any transpiled code, making it more reliable that warnings are for real environment variables, rather than bundle-shimmed variables or the like.

What do errors look like?

Coloured text. Hopefully, helpfully coloured: