Erik Toth

shutdown middleware assumes a single server.

2

If a client started both http and https servers on the same kraken app, shutdown middleware would only attempt to stop one server.

Emit "change" event (or the like) when new values are set.

8

Thinking to possible future use-cases, it might be nice for consumers of this data to observe `change` events.

Update to work with hapi@8

3

Hapi 8 is GA now so we should support it.

The first registry needs to keep the host header such that npm can create the correct tarball URL via [// legacy kludge](https://github.com/isaacs/npmjs.org/blob/master/registry/shows.js#L19)

Also, ensure timeout doesn't fail, but allows for fallback.

Excise bower from the generator

3

Getting the sense that it not terribly helpful and certainly more trouble than it's worth.

Remove "engineStrict" in preparation for npm 3+

17

Upon install: ``` bash npm WARN engineStrict Per-package engineStrict (found in package.json for lusca) npm WARN engineStrict won't be used in npm 3+. Use the config setting `engine-strict` instead. ```

Since kraken still uses ^1 it would be nice to get that feature to developers.

When a Task is executed the Resource returns information as to the nature of the failure. According to the specification any error that is transferred to another state is an...