Dependency Upgrades

See changelog.

Use ioredis vs. then-redis & memoization support

(POTENTIALLY) BREAKING CHANGES. Please see CHANGELOG.md for more info, including an upgrade guide.

Ember CLI Deploy 0.5.x Support

BREAKING CHANGES. Please see CHANGELOG.md for more info, including an upgrade guide.

Rework Middleware Method Signature

BREAKING CHANGES

An inconsistency between the fetch api and middleware was fixed.

In 0.1.x, you used the middleware like this

app.use('/*', nodeEmberCliDeployRedis({
  host: 'redis.example.org',
  port: 6929,
  password: 'passw0rd!',
  database: 0
}, 'myapp'));

However, this was inconsistent with the fetchIndex method as noted by @knownasilya . To transition, please change your middleware declaration like this

app.use('/*', nodeEmberCliDeployRedis('myapp', {
  host: 'redis.example.org',
  port: 6929,
  password: 'passw0rd!',
  database: 0
}));

Expose test objects

• Test objects exposed. See the documentation for info.

ExpressJS Middleware, Then-Redis Dependency

Express Middleware

The root dependency is now usable as an express middleware. See the README for details on how to use. We exposed the fetchIndex helper method if you need to do post-processing of the index.html string retrieved from Redis.

Then-Redis Dependency

In 0.0.1, you needed to pass a connected Redis client to the helper methods. This illuminated problems with variances between clients, specifically node_redis and then-redis. To help alleviate these issues, you now pass a configuration string/object to the middleware or fetchIndex helper and we handle the connection to redis (using then-redis internally).

Initial Release

• Support for fetching the current or specified index from redis