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

iisnode-env

v1.0.3

Published

read appSettings from web.config into process.env

Downloads

61

Readme

iisnode-env

NPM version js-standard-style

iisnode-env is a zero-dependency module that loads environment variables from the <appSettings>-section of a web.config file into process.env. Storing configuration in the environment separate from code is based on The Twelve-Factor App methodology.

When hosting a node app on iisnode (for instance in an Azure WebApp), iisnode automatically provides appSettings from web.config via process.env.

As such iisnode-env does nothing if process.env.IISNODE_VERSION is defined and aims only to simplify the move between running an app inside and outside of iisnode.

Install

npm i -S iisnode-env

Usage

As early as possible in your application, require and configure iisnode-env

require('iisnode-env').config();

// or use the alias
require('iisnode-env').load();

The module will do nothing if process.env.IISNODE_VERSION is defined. In that case iisnode will have already loaded the variables.

Config

Alias: load

config will read your web.config file, parse the contents, assign it to process.env and return the loaded content or an error key if it failed.

const result = require('iisnode-env').config()

if(result.error) {
  throw result.error
}

console.log(result.parsed)

If process.env.IISNODE_VERSION is defined, config returns an empty object.

You can additionally, pass options to config

Options

Path

Default: web.config

require('iisnode-env').config({ path: '/custom/path/to/web.config' })
Encoding

Default: utf8

require('iisnode-env').config({ encoding: 'base64' })

Limits

This is i very simple module and as such there is no support (at this time) for doing this:

<appSettings file="relative file name">
</appSettings>

We only get the values we find inside of the <appSettings>-section.

Credits

Inspired by and based on

  • https://github.com/motdotla/dotenv

License

MIT: http://tolu.mit-license.org