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

@rxstack/configuration

v0.8.0

Published

RxStack Configuration Component

Downloads

50

Readme

The RxStack Configuration

The Configuration component allows you to load different configuration files depending on node environment.

Installation

npm install @rxstack/configuration --save

Documentation

The configuration.initialize() takes up to two options:

  1. Path to environment folder directory: configuration.initialize(process.env.AP_DIR + '/dist/src/configs').

  2. Files are named environment.ts or environment.testing.ts. You can change the name configuration.initialize(path_to_dir, 'config') then it will become config.ts

First you need to create environment.ts in the /src/environments folder. Let’s say we want to load different file in production environment then we need to create a new file /src/environments/environment.production.ts. The production environment will inherit all configurations from environment.ts. Under the hood it uses lodash _.mergeWith to overwrite configurations.

Example

In environments/environment.ts we want to use the local development environment:

export const environment = {
  "host": "localhost",
  "port": 3000,
  "mongodb": "mongodb://localhost:27017/myapp",
};

In environments/environment.production.ts we are going to use environment variables:

export const environment = {
  "host": "MONGO_HOST",
  "port": "MONGO_PORT",
  "mongodb": "MONGOHQ_URL",
};

Now it can be used in our app.ts like this:

import {configuration} from '@rxstack/configuration';
configuration.initialize('./environments');
import {environment} from './environments/environment';

// in development it will return localhost
environment.host

Variable types

@rxstack/configuration uses the following variable mechanisms:

  • If the value is a valid environment variable (e.v. NODE_ENV), use its value instead
  • If the value starts with ./ or ../ turn it into an absolute path relative to the application root path

Root path

You get get root path of your application: configuration.getRootPath()

License

Licensed under the MIT license.