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

archdevconfig

v1.6.5

Published

Architecode File-based Configuration Library using hostname

Downloads

23

Readme

ARCHDEVCONFIG

This is the dynamics, file-based application configuration library. The configuration file is selected by the server name.

const AppConfig = require('archdevconfig');
const appConfig = AppConfig.getInstance();

// appConfig = {
//   "name": "The name of configuration",
//   "pkgpath": "The path of the 'package.json' file, ex. /sample_application",
//   "pkgjson": "The 'package.json' file, ex. /sample_application/package.json",
//   "hostname": "The server name",
//   "configPath": "The path of configuration files, ex. /sample_application/configs",
//   "logPath": "The path of log files, ex. /sample_application/logs"
// };

Installation

$ npm install archdevconfig --save

Features

  • Stores a default configuration as the singleton
  • Loads a configuration file by hostname or setup

Usage

const AppConfig = require('archdevconfig');

1. Getting a default configuration:

const defaultConfig = AppConfig.getInstance();

The AppConfig.getInstance() returns the 'default configuration'.

2. Providing the Setup for creating the default configuration on the first call:

const defaultConfig = AppConfig.getInstance(setup);

After the default configuration created on the first call, the provided Setup will be ignored when calling the function.

SETUP:

const setup = { name: "production" };
const defaultConfig = AppConfig.getInstance(setup);
// it loads the configuration file on 'config/path/production.config.json'.
  • Name - setup the name of specified configuration file (*.config.json). If none is provided, it will use '[hostname].config.json' or 'default.config.json' as default.
const setup = { path: "./sample/configs/path" };
const defaultConfig = AppConfig.getInstance(setup);
  • Path - setup where the path of configuration files are. If none is provided, it will use 'application_location/configs' as default.
const setup = { log: "./sample/logs/path" };
const defaultConfig = AppConfig.getInstance(setup);
  • Log - setup where the path of log files are. If none is provided, it will use 'application_location/logs' as default.
// Put them all together..
const setup = { name: "production", path: "./lib/configs", log: "./lib/logs" };
const defaultConfig = AppConfig.getInstance(setup);

3. Setting the default configuration:

const defaultConfig = AppConfig.setInstance(newConfig);

It will set a new configuration to the default one.

4. Resetting the default configuration:

// defaultConfig becomes 'undefined'
const defaultConfig = AppConfig.setInstance();

It will reset the default configuration when 'undefined' is provided.

5. Loading the configuration by Setup:

const config = AppConfig.load(setup);

This loads a configuration using Setup. It will NOT change the 'default configuration'.