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

@mazp/dotenv

v1.2.2

Published

Injecting data to process.env in runtime or running the command

Downloads

12

Readme

@mazp/dotenv

Introduce

This is a package about injecting data to process.env object from a .env file, made this package reason is dotenv package is unstable.

Install

npm i @mazp/dotenv
yarn add @mazp/dotenv

Usage

Use env file inject

dotenv test.env rimraf dist

if you don't pass a .env file, default use that named config.env file in the root dir, that you can direct use command like follow:

dotenv rimraf dist

Use parameter inject

dotenv NODE_ENV=development rimraf dist

API

dotnet(option: DotenvOption)

interface DotenvOption {
  path?: string | string[];
  command?: string[];
}
declare function dotenv(option: DotenvOption): void;

you can use this API, pass the path parameter inject data to process.env, path is a .env file location, if you do not pass, default use that named config.env file in the root dir. The path parameter is a relative root dir, so you maybe use a path or url module to load the correct path.

// ESM
import dotenv from "@mazp/dotenv";
dotenv({});
// CJS
let dotenv = require("@mazp/dotenv");
dotenv({ path: "test.env" });