Update React & Webpack for webpack 2

[DanielFallon]

Couple of things coming up:

• Webpack 2 is on the horizon (we're at RC 2)
• awesome-ts-loader is in pretty bad disrepair with the breaking changes from both webpack 2 and ts 2.1.*

Should we return this documentation to using ts-loader? for simple projects, the configuration is much easier, and the simplicity of that loader plugin means that its more likely to stay up to date long term.

Thoughts?
I'll start working on changes and a pull request sometime this weekend

DJF

[mhegazy]

@DanielRosenwasser thoughts?

[DanielRosenwasser]

@TheLarkInn thoughts?

In my opinion, if ts-loader is Webpack 2-ready, ts-loader it is.

[chicoxyzzy]

It should be mentioned that code splitting with dynamic imports is currently unavailable microsoft/TypeScript#12364

[DanielFallon]

just to clarify @chicoxyzzy, that's a deficiency of the typescript syntax right now.

As a result, at-loader would be unable to handle this correct?

also a large portion of why I wanted to move back to ts-loader was because it just appears to be better maintained.

• CI build for awesome-typescript-loader/master has been broken for about 2 months
• The unit tests don't appear to reflect the currently documented API
• and there aren't a lot of contributors. ts-loader, in contrast, appears to be a fairly thin shim and has multiple significant contributors.

[chicoxyzzy]

It was just a side note. Both ts-loader and at-loader can't handle this because it is syntax error in TS. It should be clear that not all features of Webpack 2 are available with current version of TypeScript. This will prevent future misunderstanding. So if documentation will be updated for Webpack 2 it seems legit to add note about dynamic imports

[mbertram]

@orta I think this can be closed. The tutorial was updated for a current webpack version (#765).

[orta]

Great, thanks @mbertram