[DOC Beta] Fixing documentation typo (thanks to @bmac)
[BUGFIX beta] update run.throttle docs with new immediate default
[BUGFIX] Fix grouped view when using `#each foo in bar`
Cleanup JSHint errors.
Merge pull request #4854 from rjackson/cleanup-jshint-issues-with-spring-cleaning

Cleanup JSHint errors.
Merge pull request #4840 from GavinJoyce/gj/grouped-view-with-each-in

[BUGFIX] Fix GroupedEach with `#each foo in bar` syntax
Fix usage with Chrome Harmony.

Currently, the test suite fails when running with
`chrome://flags/#enable-javascript-harmony` enabled.

All of the failures were due to duplicate declarations, which apparently
fails when running with Harmony features enabled...
Merge pull request #4856 from rjackson/harmony-fixes

Fix usage with Chrome Harmony.
Broccolify.
Merge pull request #4839 from rjackson/broccolify

Broccolify
Fix build publishing.
Removed duplicate entry for pattern
Merge pull request #4860 from nadavshatz/remove-duplicate-entry

Removed duplicate entry for pattern
[BUGFIX beta] Only consider requests fired in a single test as pending

In order for the test waiter to work, it needs to keep track of ajax
calls. In the past these calls were tracked by jQuery internally-
eventually we began tracking them via ajaxSend and ajaxComplete. The
simple implementation incremented and decremented a counter.

This solution was too naive, as it meant there was no way to disregard an
xhr that had begun in testA, but was resolving in testB, from the
pending count. testB would then hang on pending XHRs started in testA.

This commit introduces an array, reset on every setupForTesting, that
keeps track of fired xhr requests. When a request completes, the array
is searched for a matching send record. If one is found, the count is
decremented. If one is not found, then the response is ignored and the
count left un-touched.

In this way, only XHRs from testA will hold up waits for testA, and only
XHRs started in testB will hold up waits for testB.
Use npm scripts for building and test.
Merge pull request #4867 from rjackson/add-build-script

Use npm scripts for building and test.
Update docs to reflect how to build.
Use production environment when building.

The prod and min assets are now generated by default.

NOTE: This does not affect running `npm start` (or `broccoli serve`).
Merge pull request #4868 from rjackson/update-docs-on-building

Update docs to reflect how to build.
Merge pull request #4869 from rjackson/use-production-by-default-for-build

Use production environment when building.