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

dotenv-parse

v1.0.1

Published

Zero dependency .env to object parser

Downloads

52

Readme

Installation

The library is available on npm

# npm install
npm install --save dotenv-parse
# yarn install
yarn add dotenv-parse

Usage

Let's say we have the following .env file:

FOO=bar
NUM=2
BOOL=false
ARR1=some,thing,that,goes,wow
# we use an asterisk here to turn off the parsing for this variable, it will be returned as a string
BLEEP=false*
# we use an asterisk in the array to turn off parsing for an array value
ARR2=ping,true*,2,100
# a string between backtick won't be parsed
STR=`some,thing,that,goes,wow`

Example usage with dotenv

import dotenv from 'dotenv';
import { parse } from 'dotenv-parse');

let env = dotenv.config({})
if (env.error) throw env.error;
env = parse(env.parsed);

console.log(env);

This will result in the following object:

{
  // String
  FOO: 'bar',
  // Number
  NUM: 2,
  // Boolean
  BOOL: false,
  // Array
  ARR1: [ 'some', 'thing', 'that', 'goes', 'wow' ],
  // NOTE: this was not parsed due to the * asterisk override above
  BLEEP: 'false',
  // NOTE: only the "true*" above was opted out through the use of an asterisk
  ARR2: [ 'ping', 'true', 2, 100 ],
  // NOTE: this was not parsed because the string was between backtick
  STR: 'some,thing,that,goes,wow'
}

Options

A second argument can be provided to dotenvParseVariables with an object of options.

The defaults are listed below:

  • assignToProcessEnv (Boolean) - defaults to true, whether or not to assign the parsed values to process.env
  • overrideProcessEnv (Boolean) - defaults to false, whether or not to override existing values in process.env