Displaying 1 to 20 from 114 results

n - Node version management

  •    Shell

Node.js version management: no subshells, no profile setup, no convoluted API, just simple.to install n to bin/n of the directory specified in the environment variable $PREFIX, which defaults to /usr/local (note that you will likely need to use sudo). To install n in a custom location (such as $CUSTOM_LOCATION/bin/n), run PREFIX=$CUSTOM_LOCATION make install.

dotenv - Loads environment variables from .env for nodejs projects.

  •    Javascript

Dotenv is a zero-dependency module that loads environment variables from a .env file into process.env. Storing configuration in the environment separate from code is based on The Twelve-Factor App methodology.As early as possible in your application, require and configure dotenv.

node-foreman - A Node.js Version of Foreman

  •    Javascript

Node Foreman is a Node.js version of the popular Foreman tool, with a few Node specific changes.Foreman is a manager for Procfile-based applications. Its aim is to abstract away the details of the Procfile format, and allow you to either run your application directly or export it to some other process management format.

node-config - Node.js Application Configuration

  •    Javascript

Node-config organizes hierarchical configurations for your app deployments. It lets you define a set of default parameters, and extend them for different deployment environments (development, qa, staging, production, etc.).




react-native-config - Bring some 12 factor love to your mobile apps!

  •    Objective-C

Module to expose config variables to your javascript code in React Native, supporting both iOS and Android. Keep in mind this module doesn't obfuscate or encrypt secrets for packaging, so do not store sensitive keys in .env. It's basically impossible to prevent users from reverse engineering mobile app secrets, so design your app (and APIs) with that in mind.

strip-json-comments - Strip comments from JSON. Lets you use comments in your JSON files!

  •    Javascript

It will replace single-line comments // and multi-line comments /**/ with whitespace. This allows JSON error positions to remain as close as possible to the original source.Also available as a gulp/grunt/broccoli plugin.

grunt-preprocess - Preprocess files based off environment configuration

  •    Javascript

The additional context on top of ENV that should be passed to templates. If NODE_ENV is not set, the task sets it to development by default.


with-env - Read and apply .env file (if exists) in the working directory.

  •    Javascript

Read and apply .env file (if exists) in the working directory.

yenv - Environment management for Node using YAML.

  •    Javascript

Manage environment stuff with YAML.Requires node v4.x or above.

user-home - Get the path to the user home directory

  •    Javascript

Returns null in the unlikely scenario that the home directory can't be found.This module was made long before os-homedir. When Node.js decided to add a native method for getting the user's home directory, I made a polyfill matching its API and decided to depend on it here, so not to have duplicate code. The main reason this one is still around is that lots of modules depend on it and I see no reason to inconvenience dependents by deprecating this. This one also gets the home directory on startup and returns a string rather than exposing a method, so it's faster, and I prefer this API. Modules are cheap in Node.js, so doesn't matter. Use whichever you prefer. I'm going to continue using this one.

username - Get the username of the current user

  •    Javascript

First tries to get the username from the SUDO_USER LOGNAME USER LNAME USERNAME environment variables. Then falls back to $ id -un on macOS / Linux and $ whoami on Windows, in the rare case none of the environment variables are set. The result is cached.Returns a Promise for the username.

run-node - Run the Node.js binary no matter what

  •    Shell

You can't always assume running $ node file.js will just work. The user might have the node binary in a non-standard location. They might be using a Node.js version manager like nvm, which is sourced in a subshell and not available from the outside. It also depends from where you're trying to run it. For example, GUI apps on macOS doesn't inherit the $PATH, so the node binary would not be found. Most projects that depend on Node.js just end up telling the user to manually set the full path to the node binary in some project specific settings. Now every project has to do this. Ugh... I prefer things to just work. With this module it will.This Bash script uses some tricks to find the Node.js binary on your system and run it.

shell-env - Get environment variables from the shell

  •    Javascript

Especially useful for Electron/NW.js apps as GUI apps on macOS doesn't inherit the environment variables defined in your dotfiles (.bashrc/.bash_profile/.zshrc/etc).Return a promise for the environment variables.

shell-path - Get the $PATH from the shell

  •    Javascript

Useful for Electron/NW.js apps as GUI apps on macOS doesn't inherit the $PATH defined in your dotfiles (.bashrc/.bash_profile/.zshrc/etc).Return a promise for the $PATH.

path-key - Get the PATH environment variable key cross-platform

  •    Javascript

It's usually PATH, but on Windows it can be any casing like Path...Use a custom environment variables object.