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

config-property-stamp

v1.1.0

Published

A stamp that uses config to read configuration into a stamp property.

Downloads

15

Readme

Build Status Coverage Status semantic-release

Config Property Stamp

A stamp (a composeable factory function) for use with stamp-it that creates an immutable deep property called config storing information from config with its' cascading configuration capabilities or an override with an arbitary configuration file you provide.

By itself you aren't gaining much, used in combination with other stamps you gain the composeable power to add the consistent config interface of the config module in an expected way.

For more information on using config

You can find detailed instructions on using config on the node-config wiki pages;

Usage

  • You need a configuration file, either an arbitrary file or in your Env config folder per config.

  • For loading up an arbitrary single config file:

// for a config file in the following path  {thepathWherethisCodeExecutes}/test/config.json
// with the following config
// {"item1": "test"}

const path = require('path');
// Factory Function.
const ConfigPropertyStamp = require('config-property-stamp');
const configPropertyStamp = ConfigPropertyStamp.create(path.join(__dirname, 'test', 'default.json'));
// configPropertyStamp is {item1: test}
  • For loading up config from default config module location:
// for a config file in the following path in your module config/default.json
// with the following config
// {"item1": "test2"}

const path = require('path');
const ConfigPropertyStamp = require('config-property-stamp');
// Looks for config in /config and cascades it all together.
const configPropertyStamp = ConfigPropertyStamp.create();
// configPropertyStamp is {item1: test2}