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

ember-cli-yaml-config

v1.0.0

Published

Addon for reading configuration from yaml files on build.

Downloads

4

Readme

ember-cli-yaml-config

Code Climate

Installation

npm install ember-cli-yaml-config --save-dev

Usage

This addon reads yaml files placed in your apps config directory – config.yml and sec_config.yml and adds keys found there to the environment object, depending in which environment you are right now.

Example

# config/config.yml
development:
  foo: bar
test:
  foo: baz
production:
  foo: biz

You can access those values through the environment object:

import config from 'your-app-name/config/environment';

// when in development environment
console.log(config.foo); #=> bar

// when in test environment
console.log(config.foo); #=> baz

// when in production environment
console.log(config.foo); #=> biz

The second file – sec_config.yml – is so you could add it to .gitignore and use it to override values from config.yml. This might be useful if you need to override something for your local machine, or if you have multiple builds of the app and link the sec_config.yml with custom values for that build as a part of the deployemnt process.

Configuration

There are two configuration options, here's how you could set them to their defaults:

// ember-cli-build.js

var EmberApp = require('ember-cli/lib/broccoli/ember-app');

module.exports = function(defaults) {
  var app = new EmberApp(defaults, {
    yamlConfig: {
      fileNames: ['config.yml', 'sec_config.yml'],
      warnAboutNonexistingFiles: false
    }
  });

  return app.toTree();
};

fileNames is used to list the .yml files to merge into config. The order is important, values from the latter files take precedence.

If warnAboutNonexistingFiles is set to true it will log a warning if any of the files specified in fileNames doesn't exist.

Fair word of warning about secrecy of the config files

Do not forget that the environment object is part of the build, which means that contents of the config files cannot be treated as "secret" by any means.

Development

Running

  • ember server
  • Visit your app at http://localhost:4200.

Running Tests

  • ember test
  • ember test --server

For more information on using ember-cli, visit http://www.ember-cli.com/.