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

reenv

v0.3.0

Published

dotenv-cli written in reason

Downloads

19

Readme

reenv

Build Status

dotenv-cli implementation in ReasonML. The goal is to have feature parity with dotenv but be implemented in Reason. If there is a feature missing please log an issue.

Installation

reenv is available on all mainstream desktop platforms (Windows, macOS and Linux) and is installable via npm.

npm install -g reenv

Usage

NAME
       reenv - Read dotenv file(s) and supply them to the program.

SYNOPSIS
       reenv [OPTION]... COMMAND [ARGS]...

ARGUMENTS
       ARGS
           Arguments passed to the command.

       COMMAND (required)
           Command to run

OPTIONS
       -e FILE, --env-file=FILE
           The .env files to read variables from.

       --help[=FMT] (default=auto)
           Show this help in format FMT. The value FMT must be one of `auto',
           `pager', `groff' or `plain'. With `auto', the format is `pager` or
           `plain' whenever the TERM env var is `dumb' or undefined.

       -s FILE, --safe=FILE
           The .env file with keys that need to be provided.

       --version
           Show version information.

EXIT STATUS
       reenv exits with the following status:

       0   on success.

       124 on command line parsing errors.

       125 on unexpected internal errors (bugs).

example

reenv -e .env -e .env.dev node index.js

simple benchmarks

Ulriks-MBP:reenv ulrik$ time dotenv -e test/.env node test/index.js
hello world!
hello world?
hello=world

real    0m0.152s
user    0m0.118s
sys     0m0.031s

Ulriks-MBP:reenv ulrik$ time reenv -e test/.env node test/index.js
hello world!
hello world?
hello=world

real    0m0.076s
user    0m0.056s
sys     0m0.015s

Ulriks-MBP:reenv ulrik$ time TEST=a TEST2=b TEST3=c node test/index.js
a
b
c

real    0m0.070s
user    0m0.053s
sys     0m0.014s

Developing:

npm install -g esy pesy
git clone <this-repo>
esy install
esy build

Running Binary:

After building the project, you can run the main binary that is produced.

esy x reenv

Running Tests:

# Runs the "test" command in `package.json`.
esy test