Class Application

Call advanceReadiness after any asynchronous setup logic has completed. Each call to deferReadiness must be matched by a call to advanceReadiness or the application will never become ready and routing will not begin.

Initialize the application and return a promise that resolves with the Application object when the boot process is complete.

Run any application initializers and run the application load hook. These hooks may choose to defer readiness. For example, an authentication hook might want to defer readiness until the auth token has been retrieved.

By default, this method is called automatically on "DOM ready"; however, if autoboot is disabled, this is automatically called when the first application instance is created via visit.

Create an ApplicationInstance for this application.

Use this to defer readiness until some condition is true.

Example:

import Application from '@ember/application';

let App = Application.create();

App.deferReadiness();

fetch('/auth-token')
.then(response => response.json())
.then(data => {
  App.token = data.token;
  App.advanceReadiness();
});

This allows you to perform asynchronous setup logic and defer booting your application until the setup has finished.

However, if the setup requires a loading UI, it might be better to use the router for this purpose.

The goal of initializers should be to register dependencies and injections. This phase runs once. Because these initializers may load code, they are allowed to defer application readiness and advance it. If you need to access the container or store you should use an InstanceInitializer that will be run after all initializers and therefore after all code is loaded and the app is ready.

Initializer receives an object which has the following attributes: name, before, after, initialize. The only required attribute is initialize, all others are optional.

• name allows you to specify under which name the initializer is registered. This must be a unique name, as trying to register two initializers with the same name will result in an error.

import { debug } from '@ember/debug';

export function initialize() {
  debug('Running namedInitializer!');
}

export default {
  name: 'named-initializer',
  initialize
};

• before and after are used to ensure that this initializer is ran prior or after the one identified by the value. This value can be a single string or an array of strings, referencing the name of other initializers.

An example of ordering initializers, we create an initializer named first:

import { debug } from '@ember/debug';

export function initialize() {
  debug('First initializer!');
}

export default {
  name: 'first',
  initialize
};

// DEBUG: First initializer!

We add another initializer named second, specifying that it should run after the initializer named first:

import { debug } from '@ember/debug';

export function initialize() {
  debug('Second initializer!');
}

export default {
  name: 'second',
  after: 'first',
  initialize
};

// DEBUG: First initializer!
// DEBUG: Second initializer!

Afterwards we add a further initializer named pre, this time specifying that it should run before the initializer named first:

import { debug } from '@ember/debug';

export function initialize() {
  debug('Pre initializer!');
}

export default {
  name: 'pre',
  before: 'first',
  initialize
};

// DEBUG: Pre initializer!
// DEBUG: First initializer!
// DEBUG: Second initializer!

Finally we add an initializer named post, specifying it should run after both the first and the second initializers:

import { debug } from '@ember/debug';

export function initialize() {
  debug('Post initializer!');
}

export default {
  name: 'post',
  after: ['first', 'second'],
  initialize
};

// DEBUG: Pre initializer!
// DEBUG: First initializer!
// DEBUG: Second initializer!
// DEBUG: Post initializer!

• initialize is a callback function that receives one argument, application, on which you can operate.

Example of using application to register an adapter:

import ApiAdapter from '../utils/api-adapter';

export function initialize(application) {
  application.register('api-adapter:main', ApiAdapter);
}

export default {
  name: 'post',
  after: ['first', 'second'],
  initialize
};

Instance initializers run after all initializers have run. Because instance initializers run after the app is fully set up. We have access to the store, container, and other items. However, these initializers run after code has loaded and are not allowed to defer readiness.

Instance initializer receives an object which has the following attributes: name, before, after, initialize. The only required attribute is initialize, all others are optional.

• name allows you to specify under which name the instanceInitializer is registered. This must be a unique name, as trying to register two instanceInitializer with the same name will result in an error.

import { debug } from '@ember/debug';

export function initialize() {
  debug('Running named-instance-initializer!');
}

export default {
  name: 'named-instance-initializer',
  initialize
};

• before and after are used to ensure that this initializer is ran prior or after the one identified by the value. This value can be a single string or an array of strings, referencing the name of other initializers.

• See Application.initializer for discussion on the usage of before and after.

Example instanceInitializer to preload data into the store.

export function initialize(application) {
    var userConfig, userConfigEncoded, store;
    // We have a HTML escaped JSON representation of the user's basic
    // configuration generated server side and stored in the DOM of the main
    // index.html file. This allows the app to have access to a set of data
    // without making any additional remote calls. Good for basic data that is
    // needed for immediate rendering of the page. Keep in mind, this data,
    // like all local models and data can be manipulated by the user, so it
    // should not be relied upon for security or authorization.

    // Grab the encoded data from the meta tag
    userConfigEncoded = document.querySelector('head meta[name=app-user-config]').attr('content');

    // Unescape the text, then parse the resulting JSON into a real object
    userConfig = JSON.parse(unescape(userConfigEncoded));

    // Lookup the store
    store = application.lookup('service:store');

    // Push the encoded JSON into the store
    store.pushPayload(userConfig);
}

export default {
  name: 'named-instance-initializer',
  initialize
};

Registers a factory that can be used for dependency injection (with inject) or for service lookup. Each factory is registered with a full name including two parts: type:name.

A simple example:

import Application from '@ember/application';
import EmberObject from '@ember/object';

let App = Application.create();

App.Orange = EmberObject.extend();
App.register('fruit:favorite', App.Orange);

Ember will resolve factories from the App namespace automatically. For example App.CarsController will be discovered and returned if an application requests controller:cars.

An example of registering a controller with a non-standard name:

import Application from '@ember/application';
import Controller from '@ember/controller';

let App = Application.create();
let Session = Controller.extend();

App.register('controller:session', Session);

// The Session controller can now be treated like a normal controller,
// despite its non-standard name.
App.ApplicationController = Controller.extend({
  needs: ['session']
});

Registered factories are instantiated by having create called on them. Additionally they are singletons, each time they are looked up they return the same instance.

Some examples modifying that default behavior:

import Application from '@ember/application';
import EmberObject from '@ember/object';

let App = Application.create();

App.Person = EmberObject.extend();
App.Orange = EmberObject.extend();
App.Email = EmberObject.extend();
App.session = EmberObject.create();

App.register('model:user', App.Person, { singleton: false });
App.register('fruit:favorite', App.Orange);
App.register('communication:main', App.Email, { singleton: false });
App.register('session', App.session, { instantiate: false });

Reset the application. This is typically used only in tests. It cleans up the application in the following order:

1. Deactivate existing routes
2. Destroy all objects in the container
3. Create a new application container
4. Re-route to the existing url

Typical Example:

import Application from '@ember/application';
let App;

run(function() {
  App = Application.create();
});

module('acceptance test', {
  setup: function() {
    App.reset();
  }
});

test('first test', function() {
  // App is freshly reset
});

test('second test', function() {
  // App is again freshly reset
});

Advanced Example:

Occasionally you may want to prevent the app from initializing during setup. This could enable extra configuration, or enable asserting prior to the app becoming ready.

import Application from '@ember/application';
let App;

run(function() {
  App = Application.create();
});

module('acceptance test', {
  setup: function() {
    run(function() {
      App.reset();
      App.deferReadiness();
    });
  }
});

test('first test', function() {
  ok(true, 'something before app is initialized');

  run(function() {
    App.advanceReadiness();
  });

  ok(true, 'something after app is initialized');
});

Boot a new instance of ApplicationInstance for the current application and navigate it to the given url. Returns a Promise that resolves with the instance when the initial routing and rendering is complete, or rejects with any error that occurred during the boot process.

When autoboot is disabled, calling visit would first cause the application to boot, which runs the application initializers.

This method also takes a hash of boot-time configuration options for customizing the instance's behavior. See the documentation on ApplicationInstance.BootOptions for details.

ApplicationInstance.BootOptions is an interface class that exists purely to document the available options; you do not need to construct it manually. Simply pass a regular JavaScript object containing of the desired options:

MyApp.visit("/", { location: "none", rootElement: "#container" });

Supported Scenarios

While the BootOptions class exposes a large number of knobs, not all combinations of them are valid; certain incompatible combinations might result in unexpected behavior.

For example, booting the instance in the full browser environment while specifying a foreign document object (e.g. { isBrowser: true, document: iframe.contentDocument }) does not work correctly today, largely due to Ember's jQuery dependency.

Currently, there are three officially supported scenarios/configurations. Usages outside of these scenarios are not guaranteed to work, but please feel free to file bug reports documenting your experience and any issues you encountered to help expand support.

Browser Applications (Manual Boot)

The setup is largely similar to how Ember works out-of-the-box. Normally, Ember will boot a default instance for your Application on "DOM ready". However, you can customize this behavior by disabling autoboot.

For example, this allows you to render a miniture demo of your application into a specific area on your marketing website:

import MyApp from 'my-app';

$(function() {
  let App = MyApp.create({ autoboot: false });

  let options = {
    // Override the router's location adapter to prevent it from updating
    // the URL in the address bar
    location: 'none',

    // Override the default `rootElement` on the app to render into a
    // specific `div` on the page
    rootElement: '#demo'
  };

  // Start the app at the special demo URL
  App.visit('/demo', options);
});

Or perhaps you might want to boot two instances of your app on the same page for a split-screen multiplayer experience:

import MyApp from 'my-app';

$(function() {
  let App = MyApp.create({ autoboot: false });

  let sessionId = MyApp.generateSessionID();

  let player1 = App.visit(`/matches/join?name=Player+1&session=${sessionId}`, { rootElement: '#left', location: 'none' });
  let player2 = App.visit(`/matches/join?name=Player+2&session=${sessionId}`, { rootElement: '#right', location: 'none' });

  Promise.all([player1, player2]).then(() => {
    // Both apps have completed the initial render
    $('#loading').fadeOut();
  });
});

Do note that each app instance maintains their own registry/container, so they will run in complete isolation by default.

Server-Side Rendering (also known as FastBoot)

This setup allows you to run your Ember app in a server environment using Node.js and render its content into static HTML for SEO purposes.

const HTMLSerializer = new SimpleDOM.HTMLSerializer(SimpleDOM.voidMap);

function renderURL(url) {
  let dom = new SimpleDOM.Document();
  let rootElement = dom.body;
  let options = { isBrowser: false, document: dom, rootElement: rootElement };

  return MyApp.visit(options).then(instance => {
    try {
      return HTMLSerializer.serialize(rootElement.firstChild);
    } finally {
      instance.destroy();
    }
  });
}

In this scenario, because Ember does not have access to a global document object in the Node.js environment, you must provide one explicitly. In practice, in the non-browser environment, the stand-in document object only needs to implement a limited subset of the full DOM API. The SimpleDOM library is known to work.

Since there is no DOM access in the non-browser environment, you must also specify a DOM Element object in the same document for the rootElement option (as opposed to a selector string like "body").

See the documentation on the isBrowser, document and rootElement properties on ApplicationInstance.BootOptions for details.

Server-Side Resource Discovery

This setup allows you to run the routing layer of your Ember app in a server environment using Node.js and completely disable rendering. This allows you to simulate and discover the resources (i.e. AJAX requests) needed to fulfill a given request and eagerly "push" these resources to the client.

import BrowserNetworkService from 'app/services/network/browser';
import NodeNetworkService from 'app/services/network/node';

// Inject a (hypothetical) service for abstracting all AJAX calls and use
// the appropriate implementation on the client/server. This also allows the
// server to log all the AJAX calls made during a particular request and use
// that for resource-discovery purpose.

export function initialize(application) {
  if (window) { // browser
    application.register('service:network', BrowserNetworkService);
  } else { // node
    application.register('service:network', NodeNetworkService);
  }
};

export default {
  name: 'network-service',
  initialize: initialize
};

import Route from '@ember/routing/route';
import { service } from '@ember/service';

// An example of how the (hypothetical) service is used in routes.

export default class IndexRoute extends Route {
  @service network;

  model(params) {
    return this.network.fetch(`/api/posts/${params.post_id}.json`);
  }

  afterModel(post) {
    if (post.isExternalContent) {
      return this.network.fetch(`/api/external/?url=${post.externalURL}`);
    } else {
      return post;
    }
  }
}

// Finally, put all the pieces together

function discoverResourcesFor(url) {
  return MyApp.visit(url, { isBrowser: false, shouldRender: false }).then(instance => {
    let networkService = instance.lookup('service:network');
    return networkService.requests; // => { "/api/posts/123.json": "..." }
  });
}