Alexander Kalnoy

This may happen because deleting a node deletes it descendants, and you're selecting all trashed nodes, so there maybe a situation when you're trying to delete a node twice. Try...

Please make a unit test that fails without this fix.

If you're using only Eloquent, you need it to generate events properly and for this, dispatcher should be set up

Yes, but you need to set dispatcher on Eloquent

Please use other locking mechanics like RedLock when performing updates on nodes to avoid dead locks. This package will only be updated to the latest versions of Laravel, no more...

Hm... This is not a great solution either. I wouldn't want to run hidden queries. Maybe I should handle soft deleting differently, like maybe making nodes rooted.

You'll have to calculate article count for each node separetely. Or just store the value and update whenever articles added or nodes moved.

If you or someone sponsor this

UUID keys must an optional feature, so you can't change default schema for everyone

The only way to display a tree with pagination is display only root nodes with possibility to expand it and load children via ajax