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

@clouudsoftware/environment

v0.2.0

Published

Simple wrapper to get environment variables in the right format

Downloads

4

Readme

Node.js Package

@clouudsoftware/environment

Simple wrapper around process.env to provide the environment variable in the right Type depending on the method called.

This package doesn't dictate how environment variables become defined, it's purpose is to simply get them - during runtime - in the right Type

Available Methods

  • asArray(key: string, separator: string = ',')
  • asBoolean(key: string)
  • asJson(key: string)
  • asNumber(key: string)
  • env(key: string)

Usage

asArray(key, separator)

By default, the separator (second parameter) is ,. You can pass in any value you like here as long as it is a valid string.

Take the string 'one,two,three,four,five' as our starting position, and let's say it's behind process.env['numberArray'] calling the method asArray('numberArray') will reutrn a result of:

[
  'one',
  'two',
  'three',
  'four',
  'five
]

Since we used commas as the separator we didn't need to define it as the second parameter as it takes a comma as the default value.

asBoolean(key)

If the value is any of the below, you will receive true, otherwise false will be returned

  • true
  • 1
  • y
  • Y

asJson(key)

If the value does not convert to a JSON object, you will receive a TypeError

asNumber(key)

If the value does not convert to a number, you will receive a TypeError

env(key)

This is the underlying method to get the proces.env. Calling this method will return the raw environment variable in String format