Sadly, I think we are going to see more of these bugs appear in dSteem. It has been a somewhat stable library, but now that Steemit's own library has pulled ahead, it's not going to be a feasible choice soon enough.

The advantage of dSteem used to be its asynchronous methods allowing you to use async/awaitwith them without needing to use the old Node-style callbacks and wrap in a Promise. But, for over a year now the steem-js package uses Promise.promisfy to wrap those Node-style callbacks for us.

I ditched using dSteem a little while ago, especially after all of that crap the dev tried pulling which caused STINC to power down their stake and the whole back and forth situation with Ned.

The upside of dSteem still is the documentation. The documentation sucks for the steem-js package, but it would make for a good community contribution if someone wanted to dig through the code. The unit tests are the real documentation for it at present.