fastboot

FastBoot

FastBoot is a library for rendering Ember.js applications in Node.js.

For more information about FastBoot, see www.ember-fastboot.com, the Ember CLI addon that's a prerequisite for developing FastBoot apps.

To serve server-rendered versions of your Ember app over HTTP, see the FastBoot App Server.

FastBoot requires Node.js v4 or later.

Usage

const FastBoot = require('fastboot');

let app = new FastBoot({
  distPath: 'path/to/dist'
});

app.visit('/photos')
  .then(result => result.html())
  .then(html => res.send(html));

In order to get a dist directory, you will first need to build your Ember application, which packages it up for using in both the browser and in Node.js.

Build Your App

To get your Ember.js application ready to both run in your user's browsers and run inside the FastBoot environment, run the Ember CLI build command:

$ ember build --environment production

(You will need to have already set up the Ember CLI FastBoot addon. For more information, see the FastBoot quickstart.)

Once this is done, you will have a dist directory that contains the multi-environment build of your app. Upload this file to your FastBoot server.

Command Line

You can start a simple HTTP server that responds to incoming requests by rendering your Ember.js application using the ember-fastboot command:

$ ember-fastboot path/to/dist --port 80

Debugging

Run fastboot with the DEBUG environment variable set to fastboot:* for detailed logging.

Changelog

1.0.0-beta.1

• This version is a significant change from previous versions.
• Responsibility for serving HTTP requests has been extracted to the fastboot-express-middleware and fastboot-app-server repositories.
• The name of this project has been changed to reflect the reduction in responsibilities: it is now just fastboot, a library for rendering Ember apps on the server, instead of fastboot-app-server.
• The minimum required Node version is now v4. Support for 0.12 will be added later via transpiling.
• Adds a resilient mode, where errors during rendering are suppressed and a blank HTML page is returned instead.
• JSHint has been added to the automated tests.
• Calling visit() returns a Result object that encapsulates the rendered result.