Bump deps and fixed tests

[robertsLando]

@mcollina

I don't know if this was wanted or no. In [email protected] the only stream error thrown was 'ECONNREFUSED' but in [email protected] now it throws all this errors:

var socketErrors = [
  'ECONNREFUSED',
  'EADDRINUSE',
  'ECONNRESET',
  'ENOTFOUND'
]

Source: https://github.com/mqttjs/MQTT.js/pull/1076/files#diff-50cfa59973c04321b5da0c6da0fdf4feR30

Here you see the commit that has changed this: https://github.com/mqttjs/MQTT.js/pull/1076/files#diff-50cfa59973c04321b5da0c6da0fdf4feL325

[github-actions]

Pull Request Test Coverage Report for Build 90973369

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 99.724%

---

Totals
Change from base Build 90900640:	0.0%
Covered Lines:	775
Relevant Lines:	775

---

💛 - Coveralls

[mcollina]

lgtm

[robertsLando]

About your LGTM @mcollina, I don't understand if the answer to my question

I don't know if this was wanted or no. In [email protected] the only stream error thrown was 'ECONNREFUSED' but in [email protected] now it throws all this errors:

Is yes it is wanted or not it should not work like that. The connection is closed and I think that that error should not be thrown by the client. The stream has been closed correctly

[mcollina]

tests are passing and code is ok for me. I didn’t understand your question.

[robertsLando]

@mcollina I don't think mqtt client should throw that error when closing client. That's why my question

I think that once the stream is closed using client end there should be no error thrown by the stream

[mcollina]

I don’t know and it does not matter for Aedes. There are a few new folks that are working on MQTT.js.