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

@kuoki/environment

v2.0.0

Published

An Asynchronous Environment Manager for JavaScript and TypeScript Applications

Downloads

2

Readme

Environment

An Asynchronous Environment Manager for JavaScript and TypeScript Applications.

npm Documentation Coverage Quality Gate Status GitHub GitHub issues environment

About The Project

This library provides tools to manage environment properties in browser based JavaScript and TypeScript applications.

The common way to manage the application properties in browser based JavaScript frameworks is to define environment values in a constant or env file and load them at build stage. This strategy is not suitable for developments where, for example, the final build is deployed in a repositoy manager such as Nexus or Artifactory and reused in diferent environments, or in a microservices architecture where the properties are loaded from a config manager service. This library addresses this and other gaps by allowing, among others, the following behaviors:

  • Get properties from constants
  • Get properties from local sources, such as files
  • Get properties from remote HTTP sources, such as a REST API
  • Get properties from remote streaming sources, such as a WebSocket server
  • Get properties from sources with interdependencies
  • Get properties from multiple sources in order, unordered or by mixing strategies
  • Stop source or application loading after a trigger
  • Wait until required sources or properties are setted to load the application
  • Define if the properties from a source should overwrite the existing ones or to merge with them
  • Manage the loading lifecycle with hooks
  • Implement a middleware to intercept the added properties

Getting Started

Installation

Using NPM

npm install --save @kuoki/environment

Using Yarn

yarn add @kuoki/environment

Dependencies

Usage

The steps to generate an environment manager are described below. Each of the steps is described in depth, with examples and common hacks, in the documentation of each module.

  1. Implement and instantiate an EnvironmentStore to store the environment properties.
  2. Implement and instantiate an EnvironmentService to mutate the environment state.
  3. Implement and instantiate an EnvironmentQuery to get the environment properties.
  4. Implement and instantiate as many EnvironmentSource as needed to get the environment properties.
  5. Implement and instantiate an EnvironmentLoader to get the properties from the sources.

There is a faster way to get started if you want to use all the default implementations, which is to use createEnvironmentModule(), a factory that creates an EnvironmentModule and starts the load of properties.

import { createEnvironmentModule, EnvironmentModule, EnvironmentQuery, EnvironmentSource } from '@kuoki/environment';

// env.json = { userName: 'JohnDoe01' }
const fileSource: EnvironmentSource = {
  isRequired: true,
  load: async () => fetch('env.json').then((response) => response.json())
};
const constSource: EnvironmentSource = {
  isRequired: true,
  load: () => [{ name: 'John Doe' }]
};
const environmentModule: EnvironmentModule = await createEnvironmentModule([fileSource, constSource]);
export const env: EnvironmentQuery = environmentModule.query;

env.getAll(); // {name:'John Doe',userName:'JohnDoe01'}