v0.0.11

Mostly a cleanup release with some new features to improve DX.

• This addon now disables itself during production builds
• A new ember-try scenario for FastBoot 2.0
• Runtime check to make sure the host app has ember-cli-fastboot installed

v0.0.10

Internal fixes

• Upgraded add-on docs
• Make sure localhost is in the whitelist for both test and development environments.
• If the beta try scenario fails then the build will fail

v0.0.9

This release fixed some internals of FastBoot testing that were causing bugs and unexpected behavior.

Potential breaking change

Previously, this addon set the FastBoot host to ember-cli-fastboot-testing.localhost when rendering the FastBoot application. This could lead to unexpected behavior when fetching data from from FastBoot.

In order to make data fetching easier to reason about, the FastBoot host is now the same as the browser executing the FastBoot tests. The reason for this change is that this behavior now fits with the mental model of how a production FastBoot app would function.

As an example, If you are using testem, the host given to FastBoot would be localhost:7357. While running in test mode, FastBoot testing whitelists localhost:*.

Unless you were writing code that specifically checked for the host ember-cli-fastboot-testing.localhost you can safely ignore this change.

Internal fixes

• Upgraded add-on docs
• Removed ember-fetch, added whatwg-fetch (fixes #21)
• Pin tough-cookie

v0.0.8

Adds the ability to customize the HTTP request headers sent to fastboot.

v0.0.7

Fetch is now a dependency since it's needed to test the host app.

v0.0.6

Fastboot now uses the browser's headers when rendering on the server. This fixed a bug where a missing user-agent was crashing another addon's fastboot rendering logic.

v0.0.5

Fixed a bug where the request object in the fastboot service had null or undefined values. #1

v0.0.4

Fixed a bug where query params weren't correctly sent to fastboot. #10

v0.0.3

Bugfixes

v0.0.2

Bugfixes