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

@skyline-js/env

v0.0.2

Published

A library for managing environment variables

Downloads

5

Readme

Parsing environment variables does not have to be chaotic. The @skyline-js/env package provides a clean API for parsing and validating environment variables as well as setting deafults for different environments (e.g., development, CI/CD, production). The question "What value does this environment variable have in production?" should be easy to answer without having to go through deployment scripts. Rely on each environment variable to be parsed and validated at the start-up of your application, so a missing authentication token is immediately spotted on deployment and not afterwards when the authentication token is needed to fullfill a request.

The @skyline-js/env package allows you to:

  • Parse environment variables of any data type (boolean, number, string, ...), an array of a basic data type or as an JSON object.
  • Validate the value of an environment variable such has minimum and maximum for numbers, regular expression matching for strings and so on.
  • Provide default values for different environments (development, CI/CD, production, ...)
  • Encryption and decryption of sensitive content with a master key (secrets vault pattern)

Getting started

Install @skyline-js/env using your preferred package manager:

npm install @skyline-js/env

This is a minimal example of how to parse an environment variable:

const parser = new SkylineEnv();

export const env = {
  dbHost: parser.parseString('SERVER_DB_HOST'),
  dbPassword: parser.parseString('SERVER_DB_PASS'),
  dbSecureConnection: parser.parseBoolean('SERVER_DB_SECURE_CONNECTION'),
};