Name: fastboot-express-middleware
Owner: simplabs
Description: An Express middleware for rendering Ember apps with FastBoot
Created: 2016-08-01 20:59:58.0
Updated: 2016-08-01 20:59:59.0
Pushed: 2017-12-04 10:56:06.0
Homepage: null
Size: 1025
Language: JavaScript
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
This middleware is a small wrapper around the fastboot package, which renders Ember.js apps in Node.js.
By adding this middleware to your Express app, you can serve HTML from a
rendered Ember.js app to clients that don't support JavaScript, such as
curl, search crawlers, or users with JavaScript disabled.
Note that this is just an Express middleware and there is more needed to serve apps in a production environment. If you want to server-side rendered Ember applications without doing a lot of work, you are recommended to consider the FastBoot App Server, which manages many of the hard parts for you.
That said, this middleware is designed to be easy to integrate for those who already have existing Express stacks, or who want maximum flexibility in how requests are handled.
t express = require('express');
t fastbootMiddleware = require('fastboot-express-middleware');
app = express();
get('/*', fastbootMiddleware('/path/to/dist'));
listen(3000, function () {
nsole.log('FastBoot app listening on port 3000!');
Before you can use your app with FastBoot, you must first install the
ember-cli-fastboot addon and build your app by
running ember build. The build process will compile your app into a
version that is compatible with both Node.js and the browser and put it
in the dist directory. This dist directory is the path you should
provide to the middleware to specify which Ember app to load and render.
By default, errors during render will cause the middleware to send an
HTTP 500 status code as the response. In order to swallow errors and
return a 200 status code with an empty HTML page, set the resilient flag to
true:
get('/*', fastbootMiddleware({
stPath: '/path/to/dist',
silient: true
Resilient mode still calls next(err) to propagate your error to any subsequent
middleware that you apply after this one.
You can use this feature to track errors or log analytics.
However, because FastBoot is reslient still sends the response to the client.
You cannot alter the response with any of your post-fastboot middleware.
For more control over the FastBoot instance that is created to render the Ember app, you can pass a custom instance that the middleware will use instead of creating its own:
fastboot = new FastBoot({
stPath: 'path/to/dist'
middleware = fastbootMiddleware({
stboot: fastboot
get('/*', middleware);
..later
boot.reload();
npm test