@bahmutov/print-env
Prints all environment variables that start with given string
Last updated a month ago by bahmutov .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install @bahmutov/print-env 
SYNC missed versions from official npm registry.

@bahmutov/print-env renovate-app badge

Prints all environment variables that start with given string(s)

NPM

Build status semantic-release js-standard-style

Installation and usage

Requires Node version 6 or above.

Usually on your CI, you can just install this CLI tool globally

npm install -g @bahmutov/print-env
$ print-env
Usage: print-env [options] <PREFIX>...

Finds and prints the names and values of all environment variables present that start with any of the PREFIXes

Options:
  -e, --exists  Print only variable names
  -h, --help    display help for command

Call the tool with 1 or more prefixes, for example to show all vars beginning with TRAVIS or NODE:

$ print-env TRAVIS NODE
NODE_ENV=development
TRAVIS_BRANCH=master
TRAVIS_SUDO=false
TRAVIS_NODE_VERSION=8
TRAVIS_PRE_CHEF_BOOTSTRAP_TIME=2017-08-29T02:16:18
...

Variables are sorted alphabetically.

You can also check if sensitive variables are present using the -e|--exists command with the desired prefixes, in which case only the names of environment variables are printed:

$ print-env -e GH
Found environment variables that start with GH:
GH_API_KEY
GH_INSTALLATION_ID
...

exit code

If there are no variables starting with the given prefix, the tool with exit with code 1

$ print-env -e FOO
No environment variables found that start with FOO

$ echo $?
1

npx

You can run this tool without installing it permanently using npx command

$ npx @bahmutov/print-env --exists USER
npx: installed 1 in 0.737s
Found environment variables that start with USER:
USER

$ npx @bahmutov/print-env USER
npx: installed 1 in 1.975s
Found environment variables that start with USER:
USER=gleb

Publishing new version

New versions are automatically published to NPM from CI using semantic-release tool. In order for new version to be published, there should be commits since the last published version that have the subject with semantic convention.

fix: stop graphite breaking when too much pressure applied | patch release
feat: explain the feature | minor release

When making pull request, edit the title of the squashed commit - this is what semantic release will look at to decide if a new version should be published or not. If you forget, no big deal, just push an empty commit with desired release subject

git commit --allow-empty -m "feat: new exciting feature"
git push

About

Author

Gleb Bahmutov <gleb.bahmutov@gmail.com> © 2017

Collaborators

License

MIT - do anything with the code, but don't blame me if it does not work.

Support

If you find any problems with this module, email / tweet / open issue on Github

Current Tags

  • 2.1.1                                ...           latest (a month ago)

11 Versions

  • 2.1.1                                ...           a month ago
  • 2.1.0                                ...           a month ago
  • 2.0.2                                ...           2 months ago
  • 2.0.1                                ...           2 months ago
  • 2.0.0                                ...           2 months ago
  • 1.3.0                                ...           2 months ago
  • 1.2.1                                ...           2 months ago
  • 1.2.0                                ...           a year ago
  • 1.1.0                                ...           2 years ago
  • 1.0.1                                ...           3 years ago
  • 1.0.0                                ...           3 years ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 15
Last Month 64
Dependencies (2)
Dev Dependencies (12)
Dependents (1)

Copyright 2014 - 2016 © taobao.org |