Tony Brix

I actually think the plugin order is necessary. how else is it possible to always show find-and-replace above cursor-line? (Which I think it obviously should). I'm fine with it not...

according to https://github.com/esdoc/esdoc/issues/556#issuecomment-573501076 that is not an actively maintained fork of esdoc. Maybe we should try https://github.com/esdoc-next/esdoc-next

Also I'm not sure if I'm doing something wrong but that package does not seem to work. ### steps to reproduce 1. run `npm run esdoc` 2. open `pages/index.html` in...

I'm not 100% sure but I think the error is saying that it expected an int and received a bit string. This might be an issue with the server.

I don't think so (I've never used ExtendedDN). Is there something extra the client would have to send along with the filter? PRs are always welcome 😁👍

It looks like you are resolving the first search before the second search returns a value.

```js client.search(..., function (err, res) { res.on('searchEntry', function (entry) { console.log(1); client.search(..., function (err2, res2) { res2.on('searchEntry', function (entry2) { console.log(2); }); }); }); res.on('end', function () { console.log(3); });...

You have to find a way to wait to resolve the promise until all searches are complete. Something like: ```js let searches = 0 client.search(..., function (err, res) { searches++...

PRs are always welcome. 😁

Are you subscribed to the `error` event on the server or client? Do you get any errors? It would be a lot easier for us to debug if you could...