Update to newer ES6 module draft

Fixed #5

Author: sebmarkbage

Diff for: 01 - Core/01 - Classes.js

@@ -1,7 +1,7 @@
 // Instead of using @jsx directive we import the HTML export from react-dom
 // and bind it to the JSX identifier. This models the DOM dependency explicitly.
 // The JSX transpiler uses this identifier to resolve HTML tags. E.g. JSX.div();
-import { HTML: JSX } from "react-dom";
+import { HTML as JSX } from "react-dom";
 
 // The only reason we need a React depencency here is because the base class
 // provides the this.setState method.

Diff for: 01 - Core/02 - Mixins.js

@@ -1,5 +1,5 @@
 import { Component } from "react";
-import { HTML: JSX } from "react-dom";
+import { HTML as JSX } from "react-dom";
 import { mixin } from "react-utils";
 
 // Chainable mixins

Diff for: 01 - Core/03 - Stateless Functions.js

@@ -1,6 +1,6 @@
 // Instead of using @jsx directive we import the HTML export from react-dom
 // and bind it to the JSX identifier.
-import { HTML: JSX } from "react-dom";
+import { HTML as JSX } from "react-dom";
 
 // A simple component, that isn't stateful, can be provided as a single
 // function that accepts props. This provides React with a hint that this

Diff for: 01 - Core/04 - Modules.js

@@ -9,7 +9,7 @@ import { Button } from "Button";
 
 // and can be aliases like this:
 
-import { Button: MySpecialButton } from "Button";
+import { Button as MySpecialButton } from "Button";
 
 // Another alternative is to export defaults. It's unclear which of these two
 // paradigms will win for Component modules. If default exports win popular

Diff for: 01 - Core/08 - Transferring Props.js

@@ -1,4 +1,4 @@
-import { HTML: JSX } from "react-dom";
+import { HTML as JSX } from "react-dom";
 
 // Draft