James Kerr

I haven't tried to do this yet, but I would love to add it at some point. What would those libraries need from react-arborist to do their thing?

Hi @donnguyen, I didn't document it because I wasn't sure if should be public api yet. I think the way it currently exists, it's not difficult and awkward to make...

@donnguyen sounds good. With the right css styling I'm able to make the tree items expand to fill their container. Here's a demo page: https://react-arborist.netlify.app/cities

Yeah that seems reasonable. Would you like to give it shot in a PR?

Yes, you completely control the data that you give to react-arborist. The data fetching logic is up to you. You will have to detect when to fetch the next page....

Note to add an example with infinite scrolling...

This is awesome. Thank you. Two requests: 1. Instead of deriving the path in the node, I'd like to pass it into the NodeApi constructor as a param. This way...

According to the [node docs](https://nodejs.org/api/stream.html#event-end_1)... > In the case of an error, 'end' should not be emitted. It seems to me (I could very well be wrong) like streams further...

I am having this error in reverse. I am giving node-fetch a readable stream as a post body. Before giving it to node-fetch, I pass it through a transform stream....

You're right. This is a bug. The `useSimpleTree` hook needs to be updated to accept childrenAccessor props and idAccessor props.