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

@acryps/environment

v2.7.2

Published

Environment variable manager for local development

Downloads

55

Readme

acryps environment

Environment variable manager for local development

Getting Started

npm install @acryps/environment --save-dev

Active environment by adding environment before launching your application in your scripts (will work with any tool)

tsc && node index.jstsc && environment node index.js

Define environment variables in your package.json

{
	"name": "my-application",
	"environment": {
		"host": "Application Host",
		"database": {
			"host": "Database Host",
			"+port?5432": "Database Port"
		}
	}
}

You'll automatically be prompted to enter the values required for your project. The following environment variables will automatically be passed as environment variables to the application launched by environment:

  • HOST
  • DATABASE_HOST
  • DATABASE_PORT

Access them as usual with process.env.HOST - no changes to the code required. The variables are stored in ~/.a-environment and is thus outside of your current git directory - You can store secrets too and they will never end up in your git!

Switching Settings

You may be working on a testing and staging environment. You can quickly switch between different settings in environment, just create a new environment by using

$ npx environment --switch test

This will create a new setting 'test', where you can set entirely different environment variables. You'll automatically be prompted to create new variables when you start your application again.

$ npx environment --active-setting # returns the current setting name
$ npx environment --settings # returns all available settings

Editing the values

It does not get much simpler, just use --edit with an optional prefix (case insensitive)

$ npx environment --edit
$ npx environment --edit database # only database properties
$ npx environment --edit AUTHENTICATION_ENCRYPTION # only authentication → encryption properties

Modifiers

Modifiers may be added to the names in the package configuration

  • …?default: Set a default value which will be accepted when the user does not provide a value
  • +…: Require a numeric value

Adding an uppercase letter in the variables name will automatically be expanded with a _: accessKeyACCESS_KEY

Exporting / Importing

The current configuration can be exported in various formats for import into other applications. You can send your current configuration to new team members, and they can quickly import them.

$ npx environment --export # exports as environment bundle, for import into environment
$ npx environment --import <blob> # import the environment bundle into the active setting

$ npx environment --export-json # exports as json
$ npx environment --export-shell # exports as NAME="VALUE" statements for shell scripts
$ npx environment --export-dotenv # exports as export NAME="VALUE" statements for .env files
$ npx environment --export-cluster # exports as vlcluster variable commands
$ npx environment --export-kubernetes # exports as kubernetes deployment configuration values