Make compatible with react 16

[HelveticaScenario]

createClass and PropTypes were moved into separate packages in react 16. this should not break compatibility with react 15

[JakeSidSmith]

Rather than mutating React It'd be better to pass either React.PropTypes or PropTypes into the getReorderComponent function. Same with createClass. :)

[HelveticaScenario]

i agree, i was just trying to make as few changes as i could

[HelveticaScenario]

to be fair, you shouldnt be using createClass or PropTypes at all, they have been deprecated.

[HelveticaScenario]

you are already using babel, theres no reason you cant just use es6 classes

[JakeSidSmith]

I believe I first write this lib before ES6 was a standard and so I was avoiding it. I have since not migrated as due to the lack of auto-binding in ES6 classes I thought it would likely cause more bugs and not improve the library in any noticeable way.

[HelveticaScenario]

I understand, and I dont think the way you're doing it is particularly wrong, it just isnt idiomatic anymore. and there is a way of doing auto-binding in es6 classes, you do it like this.

class ASD {
  funcName = (arg) => {
    // ...
  }
}

I do think, however, that continuing to use deprecated features when more idiomatic alternatives exist probably isnt the best way of going about things. But its up to you.

[JakeSidSmith]

That was a proposed ES7 syntax as far as I know, and so I wouldn't like to use that until it's finalized. I am currently in the middle of a re-write though, so it is unlikely v2 will ever use classes.

[JakeSidSmith]

@HelveticaScenario I will probably take some time this weekend to convert this to use ES6 classes, so don't worry about updating this PR. :)

[JakeSidSmith]

Fixed these issues in alpha.6: #94

Gonna close this PR.