Added webpack-dev-server port override

You can now override the default webpack-dev-server port of 8080 using either the grunt command line, or defining the WEBPACK_PORT environment variable.

Fixed version-bump

We were being rather disrespectful to the JSON_TABS environment when bumping version numbers based on PR comments. That wasn't very nice of us to force 2-space tabs on folks. We now properly respect the JSON_TABS environment variable (assuming, of course, it's actually an integer (or an integer in a string)

Updated to jasmine@2.3

We were using a third-party jasmine-node product, this brings us up-to-date with the official jasmine-nom package for running jasmine specs in node.

It also updates karma-jasmine to ^0.3.0 which uses jasmine-core instead of bundling it's own jasmine. This will make upgrading jasmine much easier going forward. It also brings us up to jasmine@2.3 so we can take advantage of focused specs.

This change introduces two new makefiles make/karma-targets.mk and make/e2e-targets.mk to replace make/webpack-targets.mk (although make/webpack-targets.mk is still there till the next major version bump). The new targets are:

• karma-test - for running karma specs once (like on the CI system)
• karma-watch - for running the watcher as well, so the tests are re-run whenever files change
• karma-coverage - for running the specs once, but with code coverage this time

We've also added new targets to make/node-targets.mk which replace the deprecated node-test node-coverage

• jasmine-config
• jasmine-test
• jasmine-coverage
• jasmine-coveralls

The jasmine-test and jasmine-coverage are just like their node-* counterparts. jasmine-config generates a jasmine.json file in the root of your node specs directory, and should subsequently be added to your repository (or you can generate it each time and ignore it). jasmine-coveralls reports code coverage generated by jasmine-coverage to coveralls.io

Cleaning up package.json

Merge pull request #39 from job13er/fix-wait-for-promise

Fixed bug in waitForPromise and supporting 0.10.26

Removed MOCK_APIS global setup

A project can now manage their own process.env.FOO variables in their webpack.config.js file. By doing something like:

plugins: [
    new DefinePlugin({
        'process.env': {
            'MOCK_APIS': process.env.MOCK_APIS,
        },
    }) 
]

Added e2e-test helpers

This release adds some more functionality to test-utils to help DRY up e2e specs.

Added eslint-plugin-react

Updated the peerDependency versions of eslint and http-server as well as adding eslint-plugin-react to verify React.js code better.

Drastically speeding up tests

We've updated to the latest webpack and disabled source-maps in tests by default, which drastically speeds up test execution. You can turn back on source-maps by setting the MAPS environment variable to on

MAPS=on make webpack-watch-test

or

MAPS=on grunt

Simple update to project templates for node project type

Merge pull request #24 from job13er/cleanup-node-project-template

Cleaned up the `node` project templates a bit

Updated to latest `eslint`

Updated to eslint@0.19.0 which defaults comma-dangle to never which will likely break your make lint builds. This release also comes with a new .eslintrc which switches comma-dangle to always-multiline, which may also break your build. You can update to this new .eslintrc by running make update-eslintrc in your project after updating to beaker@2.0.0.

This release also includes a new custom eslint rule no-redeclare-func to catch instances of re-defining a function on an object. For example, the following code snippet will get a lint error now:

let proto = {};
proto.foo = function () {

};

...

proto.foo = function () {

};