Extending Component instead of .createClass()

[thomas-dm]

Hello there,

I’d like to use your Packery Component without resorting to using React’s createClass() method, and extend React.Component instead to have a full ES6 syntax.

However, the component fails to mount when doing this, as React.PropTypes is undefined in your PackeryComponent function. For the record, your react-masonry-component works great this way, as React is not undefined with it.

Is there any way I could get your Packery Component to work when extending Component without forking it? I'm quite reliant on npm management, so I'd like it to work out of the box.

Thank you!

[thomas-dm]

My bad:
I had not seen that, unlike your Masonry Component, your Packery Component required React to be passed as an argument in order to work.

[cookch10]

Is there a specific reason for passing React as an argument? I too was using the react-masonry-component and this was not necessary. I was looking to switch over to this library, but this seems like an odd pattern.

It doesn't really play well in a project where we're using ES6 import statements.

[codinronan]

It seems this has been abandoned. If anyone wants a version that is being maintained, I am maintaining a fork of this (and all dependency projects) over at https://github.com/UncommonConcept/react-packery-component. I have converted it to, for now, at least use the prop-types and create-react-class libs to maintain backward and forward compatibility, and will be converting it to ES6 shortly as well.

Oh it also brings in all appropriate fixes across all forks, uses my fork of the latest packery plus fixes, etc. In other words I brought everything up to date and fixed all the reported issues I found in all the repos.

Also includes Draggabilly for those who have asked about it.