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

a-settings

v1.1.4

Published

node.js settings provider for different environments

Downloads

28

Readme

a-settings

NPM Version NPM Downloads JS Standard Style

node.js settings provider for different environments

Purpose

  • Declare env in process.argv or in NODE_ENV
  • DRY settings using root configuration and env customization
  • Improve security avoiding settings runtime reassignment or injection
  • Freeze values, avoid injection at runtime
  • Use plain js over json and env files and be free to use comments and functions without limitations
  • Simply use env vars from process env
  • Stop doing this, it's not maintanable
if(process.env.NODE_ENV == 'debug') {
  port = 1234
} else {
  port = 80
}

Quick start

In app.js and in any other .js file get settings from settings/$env
settings.env contains the env name

const http = require('http')
const settings = require('a-settings')

http.createServer((request, response) => {
  response.writeHead(200, {'Content-Type': 'text/plain'})
  response.write(`Hey, I am ${settings.env} server`)
  response.end()
}).listen(settings.port)

declare settings in settings/_root.js

const app = {
  url: '',
  name: 'myapp',
  port: 9001,
  log: {
    level: process.env.LOG_LEVEL || 'warn',
    pretty: process.env.LOG_PRETTY === 'true',
  }
}

module.exports = app

and in settings/dev.js

const app = require('./_root')

app.port = 9002
app.log.level = 'trace'
app.log.pretty = true

module.exports = app

in settings/beta.js

const app = require('./_root')

app.port = 9003
app.url = 'https://beta.myapp.com',

module.exports = app

then run app.js with dev settings

node main.js dev

or run app.js using beta settings

node main.js beta

see example/

Options

Default options are

path directory containing env settings files, default is /settings in process current working
processEnv process env name, default is NODE_ENV, so NODE_ENV=beta node app.jsv
argv process argv index, default is 2 (the third) so node app.js dev

NOTES

  • If $env is provided in both ways as NODE_ENV=beta node app.js dev, env var wins, so in this case will be beta
  • If $env is not provided, default is _root

Custom Options

to use custom otions, use .settings.js in app root directory

const path = require('path')

module.exports = {
  path: path.join(__dirname, 'settings'), 
  processEnv: 'NODE_ENV',
  argv: 2
}

verbosity

To enable verbosity, add --verbose at process

node app.js alpha --verbose

TODO

  • [ ] load options from package.json
  • [ ] validate value (async)

License

The MIT License (MIT)

Copyright (c) 2018-20

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.