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 🙏

© 2025 – Pkg Stats / Ryan Hefner

platform-config

v0.1.5

Published

Fetch and validate platform configurations more easily

Downloads

179

Readme

platform-config

Description

Fetch and validate platform configurations more easily

Installation

$ npm install --save platform-config

If you'd like to try these examples, please run gulp prepare-examples first

// ./examples/easy/index.js

'use strict';

var path = require('path');
var platformConfig = require('platform-config');

var platforms = platformConfig({
  targets: path.join(__dirname, 'targets')
});

var current = platforms.current();
console.log(current);

In targets are the following files:

// ./examples/easy/targets/development.js

'use strict';

var config = {
  description: 'BY THE POWER OF DEVELOPMENT'
};

module.exports = config;
// ./examples/easy/targets/production.js

'use strict';

var config = {
  description: 'BY THE POWER OF PRODUCTION'
};

module.exports = config;
$ node examples/easy
{ description: 'BY THE POWER OF DEVELOPMENT' }
$ node examples/easy --NODE_ENV production
{ description: 'BY THE POWER OF PRODUCTION' }
$ export NODE_ENV=production
$ node examples/easy
{ description: 'BY THE POWER OF PRODUCTION' }

You can test and unset NODE_ENV like so:

$ echo $NODE_ENV
production
$ unset NODE_ENV
$ echo NODE_ENV

Running tests

$ gulp test

Test reports are written to ./reports.

Contributing

  • Do pull requests.
  • Make sure there's tests and meaningful coverage.
  • Respect ./eslintrc.
  • Issues should go in issues.