Skip to main content
Version: 6.x


single-spa-ember is a helper library that helps implement single-spa registered application lifecycle functions (bootstrap, mount and unmount) for use with Ember.js. Check out the single-spa-ember github.

It is available on npm as single-spa-ember, and also available on bower as single-spa-ember in case you want to use it with ember cli and need to use bower.


When you are building an ember application that you want to work as a single-spa application, there are five things you need to implement:

Single-spa-ember will help you implement all of those except for the activity function.

Note that the loading and activity functions are part of the single-spa root application, whereas the bootstrap, mount, and unmount functions are part of a single-spa application



loadEmberApp(appName, appUrl, vendorUrl) is a function that helps you implement the loading function for your ember application. appName and appUrl are both strings and both required, whereas vendorUrl is an optional string.

// In the single-spa root application

import { registerApplication } from "single-spa";
import { loadEmberApp } from "single-spa-ember";

const name = "ember-app";
const app = () =>
const activeWhen = (location) => location.hash.startsWith("ember");

registerApplication({ name, app, activeWhen });


Single-spa-ember will implement the single-spa lifecyle functions for you. To use it, you call the default export as a function with a configuration object, which returns an object that has bootstrap, mount, and unmount lifecycle functions on it. The provided configuration object has the following options:

// In the ember application
import singleSpaEmber from "single-spa-ember/src/single-spa-ember";

const emberLifecycles = singleSpaEmber({
appName: "ember-app", // required
createOpts: {
// See
rootElement: "#ember-app",

export const bootstrap = emberLifecycles.bootstrap;
export const mount = emberLifecycles.mount;
export const unmount = emberLifecycles.unmount;

Usage with ember cli

For the most part, you can get applications that use ember cli to work pretty seamlessly with single-spa. Maybe the biggest thing you'll have to worry about is that ember-cli assumes that it controls the entire HTML page, whereas a single-spa application does not. However, usually we can achieve equivalent behavior by just loading the vendor and app bundles into the HTML page dynamically, instead of baking them right into the HTML page. Below is a description of the known things you should do when setting up an ember-cli application with single-spa:

First, you'll need to add single-spa-ember as a dependency to the ember project. This can be done with npm, yarn, or bower. For example:

  • npm init
  • npm install single-spa-ember or
  • bower init
  • bower install single-spa-ember --save

Add the following options to your ember-cli-build.js file:

/* eslint-env node */
"use strict";

const EmberApp = require("ember-cli/lib/broccoli/ember-app");

module.exports = function (defaults) {
let app = new EmberApp(defaults, {
autoRun: false, // Set autoRun to false, because we only want the ember app to render to the DOM when single-spa tells it to.
storeConfigInMeta: false, // We're making a single-spa application, which doesn't exclusively own the HTML file. So we don't want to have to have a `<meta>` tag for the ember environment to be initialized.
fingerprint: {
customHash: null, // This is optional, just will make it easier for you to have the same url every time you do an ember build.
// Add options here

// Tell ember how to use the single-spa-ember library - pick one of the following
// if you used npm or yarn
app.import("node_modules/single-spa-ember/amd/single-spa-ember.js", {
using: [{ transformation: "amd", as: "single-spa-ember" }],

// **or** if you used bower
app.import("bower_components/single-spa-ember/amd/single-spa-ember.js", {
using: [{ transformation: "amd", as: "single-spa-ember" }],

return app.toTree();

In your single-spa root application (which is separate from anything generated by ember cli):

// root-application.js
import * as singleSpa from "single-spa";
import { loadEmberApp } from "single-spa-ember";

singleSpa.registerApplication("ember-app", loadingFunction, activityFunction);

function activityFunction(location) {
// Only render the ember app when the url hash starts with ember
return location.hash.startsWith("ember");

// single-spa-ember helps us load the script tags and give the ember app module to single-spa.
function loadingFunction() {
const appName = "ember-app";
const appUrl = "/dist/ember-app/assets/ember-app.js";
const vendorUrl = "/dist/ember-app/assets/vendor.js"; // Optional if you have one vendor bundle used for many different ember apps
return loadEmberApp(appName, appUrl, vendorUrl);

In your app.js file (that is generated by ember cli)

// app.js (the ember application)
import Ember from "ember";
import Resolver from "./resolver";
import loadInitializers from "ember-load-initializers";
import config from "./config/environment";
import singleSpaEmber from "single-spa-ember";

// This part is generated by the ember cli
const App = Ember.Application.extend({
modulePrefix: config.modulePrefix,
podModulePrefix: config.podModulePrefix,

loadInitializers(App, config.modulePrefix);

export default App;

// This is the single-spa part
const emberLifecycles = singleSpaEmber({
App, // required
appName: "ember-app", // required
createOpts: {
// optional
rootElement: "#ember-app",

// Single-spa lifecycles.
export const bootstrap = emberLifecycles.bootstrap;
export const mount = emberLifecycles.mount;
export const unmount = emberLifecycles.unmount;