Sjs/improve memory tests

Make todo-list XPath more permissive

* Gives us a bit more flex around some frameworks

improve riotjs example

remove unnecessary update()

update Vue.js to 1.0.0

React: Remove direct DOM manipulation

Fix #1488

Turn the `<input>` into a
[Controlled Component](https://facebook.github.io/react/docs/forms.html#controlled-components)
and avoid fiddling with the DOM in an imperative way.

Fixed links for TypeScript issues/documentation.

Update bio 😮

Include all nested js in glob for typescript

Ignore js style linting in typescript examples

travis update

Ref a6144290

scalajs-react example: Update to new API

 Add jsblocks 

Hanging comma

Fix for react addons clasSset deprecated warning

use express.js server for tests; closes #1465

Fixes #1405

Use an express.js server for tests instead of http-server. The primary
reason for this is that express has an available middleware that allows
us to specificy the location of the favicon other than the root
directory. This is needed because the favicon lives in the site-assets
directory.

Backbone: remove unneeded logic in todo View

The removed check is unncecessary and also incorrectly implemented,
resulting in a test failure (the "Editing should trim entered text"
example) and flawed user interaction. This change results in 100%
passing tests and the desired user interaction.

Unneeded: the associated comment states that "Model values changes
consisting of whitespaces only are not causing change to be triggered",
and so the code manually triggers a change event when the only change to
the todo is whitespace being added at the beginning and/or end of the
todo. However, there is no need for the change event when this is the
only change. So the situation described in the comment is not a problem.
The change event triggers a re-rendering of the view, but if the only
change is whitespace at the beginning or end, which is trimmed off,
anyway, then re-rendering is pointless.

Incorrectly implemented: The code in question is
`this.model.trigger('change');`. This ultimately raises an error,
because (perhaps surprisingly) when the 'change' event is manually
triggered on a model, the model is not automatically bound as the so-to-
speak "context" of that change. This can be corrected manually like so:
`this.model.trigger('change', this.model);`. This eliminates the error
and failing test case. However, as this code is not needed, anyway, of
course it's better to simply remove it. :)

⚡️ Automated Leak Detection on CI ⚡️