Is this project still active?

[odysseus-ramsay-paylocity]

Looking to use this project, going through that activity I have not seen any updates in about half a year, is there ongoing work that @jameskerr is working on?

[ben-hearn-sb]

Honestly ive been asking the same question the last weeks...

[jameskerr]

Hello world,

I apologize for the silence. I know it's difficult to depend on a package that is not being paid attention to properly. I wrote the package a few years ago because I needed this functionality in the sidebar of our Zui electron application. That piece of the UI has not needed to be revisited in a while so I haven't had a work-related reason to work on react-arborist. I started a re-write of some major components in the #235 version 4 PR. Many many issues would be closed if that branch gets over the finish line. The big question mark for me there is how backward compatible to be with version 3. And I'd need to test it more, write a migration doc, maybe a compatibility layer, etc.

In my personal life, we had our 3rd child about 6 months ago so anyone with kids knows free time is scarce. This means much less time for non-work, non-money-generating projects such as this.

I know I will need this package again in future react projects, and when that time comes, I plan to further improve what we've got here. I hope to address the many issues in a wholistic way rather than whack-a-mole style. That is why I've held off on merging some of the PRs that folks have put up. Although I could be persuaded to change my tune there, if something obviously wrong needs to fixed.

I'm open to the idea of others sharing some responsibility for this codebase, seeing that it has become quite popular.

Let me hear all your thoughts.