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-mode-resolver

v0.1.4

Published

A custom ember-cli resolver providing a configurable way to run application in different modes

Downloads

8

Readme

ember-cli Mode Resolver

npm version Build Status Ember Observer Score

Custom resolver to allow the same route to be resolved as different modes of the application. Mode is determined by configuration. (A common use case would be a/b testing)

Installation

ember install ember-cli-mode-resolver

Usage

Configuration

In your app root (app.js) add import of the mode resolver module:

import ModeResolver from 'ember-cli-mode-resolver/resolvers/mode'

Then oveveride the default resolver with mode resolver and define mode configuration:

var App;

Ember.MODEL_FACTORY_INJECTIONS = true;

App = Ember.Application.extend({
  modulePrefix: config.modulePrefix,
  podModulePrefix: config.podModulePrefix,
  //override resolver
  Resolver: ModeResolver,
  //current mode configuration
  resolverMode: {
  	id: "a",
  	delimiter: "~"
  }
});

Naming Convention

In order to have a module used when a certain mode is configure, add a the concatenation of mode delimiter and mode id as a postfix to the module file name. For example if the mode configration is:

 resolverMode: {
  	id: "a",
  	delimiter: "~"
  }

and we have a 'fooit' route module at /routes/fooit.js, we can add an altenative 'fooit' route module that will be resolved in when mode 'a' id configured - /routes/fooit~a.js.

Pods

The equaivalent case when using pods would be an alrenative to /fooit/route.js. In this case we will create an alternative 'fooit' pod folder named 'fooit~a' and place the alternative 'route.js' module file there so alternative route module file will be at /fooit~a/route.js.

Running

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

Running Tests

  • ember test
  • ember test --server

Building

  • ember build

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