Fix for #204

[arunoda]

Fixes #204

React addons require React in a special way.
That causes Webpack to push React into the app's bundle.
This fix adds new externals entries to prevent that.

[coveralls]

Coverage remained the same at 34.211% when pulling d05909a on arunoda:fix-204 into 45e36fd on zeit:master.

[coveralls]

Coverage remained the same at 34.211% when pulling d05909a on arunoda:fix-204 into 45e36fd on zeit:master.

[rauchg]

Beautiful. Yet, pretty strange that react addons require react like that? What's the rationale?

[arunoda]

Not exactly sure. But that might be the case that, FB uses their own module resolver for React.

[rauchg]

@gaearon what's the rational behind the ./React thing?

[arunoda]

May be related. See: facebook/react#6343

[gaearon]

what's the rational behind the ./React thing?

It's just importing React entry point from the same folder. react/lib/TransitionGroup imports react/lib/React.

[arunoda]

Thanks @gaearon
Oh I forgot to see other files :D

[frol]

@arunoda Are you sure that this fix is correct?

Yes, these modules only work when packaged with the react module from npm (it does this because we need access to private APIs). If you want to use the prepackaged React and an addon, then we recommend use ReactWithAddons and map react-addons-css-transition-group to React.addons.CSSTransitionGroup.

(c) facebook/react#6343

I am not a JS expert, so I am not exactly sure, but it feels like this patch will just break the addons.

[arunoda]

@frol it works. (and it should be).
It maps the internal .React with the one we've in the bundle.
Anyway, we are getting rid of the next-bundle soon. (#406)
With that there'll be no problem like this.