Anton Melser

@100terres , things seem to have completely frozen for over a month. Have you had some external issues or have you moved on to other things? If you are just...

Pretty the only reasonable choice is for one of us lurkers to finish the work here, or move to react-dnd...

@Toshinaki , the issue https://github.com/clauderic/dnd-kit/issues/775 is exactly the same as everyone (maybe except react-dnd?) on React 18. There are open issues, maintainer says "I'll get on to it", then nothing...

@Toshinaki , ok, sorry I missed that it's a drop-in replacement. That is very interesting! Having to reimplement most of the logic can make moving to another lib a massive...

> @100terres I'm using `react-beautiful-dnd` for a few projects that required react 18 and I wasn't sure how progress was coming along so I forked your work and released [@hello-pangea/dnd](https://github.com/hello-pangea/dnd)...

> Haha, timing could have been a bit better. Did you end up migrating to dnd kit? If so how do you like it compared to react beautiful dnd? @Xhale1...

Or at the very least ping @100terres directly, so we are sure they see it ;-).

As a note for other async newcomers like myself, by far the easiest way to deal with this is just to move the entire block using querysets to a separate,...

@kellen did you find a solution for this?

@wkamer, it's worse than that, the maintainers don't even have the respect to put a message in the readme saying that it is no longer under development, in spite of...