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

@rav2040/dotenv

v1.2.1

Published

.env loader with extended feature set.

Downloads

9

Readme

@rav2040/dotenv

A non-mutating Node.js library for loading environment variables with TypeScript support.

build coverage vulnerabilities npm

Installation

npm install -D @rav2040/dotenv

Usage

With the following .env file in your project root:

FOO = "bar"

Create a new environment object (process.env will be left unchanged) by importing createEnv:

import { createEnv } from "@rav2040/dotenv";
const Env = createEnv();

Variables become accessible via the following:

const foo = Env.get("FOO"); // "bar"
const baz = Env.get("BAZ"); // undefined

You can set a variable as being required by passing true as the second argument:

const foo = Env.get("FOO", true); // "bar"
const baz = Env.get("BAZ", true); // Throws an error

JSON

Returned values will be parsed as JSON by default.

e.g. FOO is set to 42:

const foo = Env.get<number>("FOO"); // 42
console.log(typeof foo); // "number"

e.g. FOO is set to {"hello":"world"}:

const foo = Env.get<{ hello: string }>("FOO"); // { hello: "world" }
console.log(typeof foo); // "object"

Configuration

const config = {
  // ...
};
const Env = createEnv(config);

path?: string

Path of the environment file. If not set AND .env does not exist in the project root then only variables from process.env will be loaded. Otherwise variables from process.env and the environment file will be merged. Defaults to .env in the project root.

encoding?: BufferEncoding

Buffer encoding of the environment file. Defaults to "utf8".

override?: boolean

Variables set in the environment file will take precedence over existing environment variables when there are conflicts. Defaults to false.

parseJson?: boolean

Values that are valid JSON will be deserialized. Defaults to true.

License

MIT