Expected:

• Render Hello Mobx screen

Current:

• Dev environment not render anything, no console error

How to reproduce:

• yarn && yarn start
• Visit localhost:3000 on IE11

I check the build and serve it, it's fine.
Might be related to this if we use CRA
facebook/create-react-app#3367

As a start it could perform these tasks:

• lint
• compile

It should be "assertion library"

Let's try to swap out Redux for MobX, because MobX is much easier to get started with and it comes with much less boilerplate than Redux.

When building with standard boilerplate will receive same issue as here: svg/svgo#622

Can be solves as instructed, but I think this should be solved in the boilerplate.

It would be a good idea to use Recompose to enhance components:
https://github.com/acdlite/recompose

Async / await is not just for managing promises. It is the way to control synchronous / asynchronous execution on parts of the code.

Note that await may only be used in functions marked with the async keyword.

// with 
function sleep(ms) {
  // Promise here is just to accomplish the sleep functionality
  return new Promise(resolve => setTimeout(resolve, ms));
}
async function bar(x) {
    await sleep(2000); // wait for 2 seconds then return
    return x;
}
// this is incorrect, await is used without function being declared as async, will throw an error
function foo(x) {
    await bar(x);
}
// this is correct
async function foo(x) {
    await bar(x);
}

By marking the function as async,, we are able to use await ( or not ) to control if the functions called inside will be executed in synchronous or asynchronous manner.

// will return 2x after 2 seconds
async function add1(x) {
  var a = bar(x);
  var b = bar(x);
  return await a + await b; 
}

// returns 2x after 4 seconds.
async function add1(x) {
  var a = await bar(x);
  var b = await  bar(x); // starts after a is done
  return a + b;
}

This makes it possible to change the sync/async flow simply by adding or omitting await before the function call.

Hi!

Which node.js version you prefer? Would be nice to have that in the docs.

https://github.com/nordsoftware/react-boilerplate/blob/master/package.json#L45

The current version is causing an error on Code Climate:

/usr/src/app/node_modules/eslint/lib/config/config-validator.js:102
        throw new Error(message.join(""));
        ^

Error: /code/.eslintrc:
	Configuration for rule "eol-last" is invalid:
	Value "always" must be an enum value.

    at validateRuleOptions (/usr/src/app/node_modules/eslint/lib/config/config-validator.js:102:15)
    at /usr/src/app/node_modules/eslint/lib/config/config-validator.js:148:13
    at Array.forEach (native)
    at Object.validate (/usr/src/app/node_modules/eslint/lib/config/config-validator.js:147:35)
    at Object.load (/usr/src/app/node_modules/eslint/lib/config/config-file.js:394:19)
    at loadConfig (/usr/src/app/node_modules/eslint/lib/config.js:74:33)
    at getLocalConfig (/usr/src/app/node_modules/eslint/lib/config.js:177:23)
    at Config.getConfig (/usr/src/app/node_modules/eslint/lib/config.js:272:22)
    at CLIEngine.getConfigForFile (/usr/src/app/node_modules/eslint/lib/cli-engine.js:715:29)
    at module.exports (/usr/src/app/lib/validate_config.js:9:22)

https://codeclimate.com/github/nordsoftware/react-boilerplate/builds/1

Updating eslint should help:
airbnb/javascript#1088 (comment)

While looking for React libs offering Foundation (the Zurb framework for sites) integration I discovered your nice react.foundation component library, then your react-starter template offering a starter template using react-foundation and read that the starter template is deprecated in favor of react-boilerplate here. Indeed the new boilerplate looks very promising. But I was missing react-foundation integration from it. I guess for some people having it directly integrated is nice. One question also interesting for these kinds of people. Is integrating react-foundation or some other approach using Foundation easy with the postcss approach taken here. I've never used postcss before, that's why I ask.

Coverage is set up on Code Climate:

https://codeclimate.com/repos/594ad1a56cb63d656e000001/settings/test_reporter

And the CI attempts to send it coverage data:

after_script:
  - codeclimate-test-reporter < coverage/lcov.info

https://github.com/digiaonline/react-boilerplate/blob/master/.travis.yml#L14

But, looking at the last master build, there's no coverage data:

$ codeclimate-[secure]-reporter < coverage/lcov.info
/home/travis/.travis/job_stages: line 57: coverage/lcov.info: No such file or directory

https://travis-ci.org/digiaonline/react-boilerplate/jobs/272035507#L477

Upgrade to React Router v4 as it's stable now.

It would also be good to add react-router-redux to this boilerplate.

webpack-contrib/extract-text-webpack-plugin#386

Can be fixed by upgrading extract-text-plugin ^2.1.0 to enable ignoreOrder-flag (https://github.com/webpack-contrib/extract-text-webpack-plugin)

Then edit config in webpack/production.babel.js for example:
const extractStylesPlugin = new ExtractTextPlugin({filename: '[name].[hash].css', ignoreOrder: true})

If we want other folks to use this awesome boilerplate, documentation should to be written and structured in a way that takes through every step (ideally, without jumping back and fourth) to a stage where all the essentials are set up, app is running and user knows where to look for information to proceed.
Right now information is scattered among Table of contents with essential tools and optional tools are mixed together.

1. Clone project & run these lines to get everything installed
2. Folder structure with explanation why it's like that and what each file does
3. How to start the whole thing (with introduction of essential modules/components)
4. Possible next steps to take
5. Links to non-essential modules and how can they be used with this boilerplate
   We have most of that information already, it's just fragmented and scattered over docs.
   Ideally, a beginner should be able to set up a project just by reading the doc and have a clear understanding where he/she can find information to proceed

This has been a recurring issue previously. IMO devDependencies should be used only for things required for testing and developing, such as Mocha and the Webpack dashboard.

Can these old feature branches be deleted, or pull requested?

https://github.com/digiaonline/react-boilerplate/branches/stale