Filipe Pomar
Filipe Pomar
I have exposed the topic validation functions (alongside with their types) in order to allow third parties to benefit of their use without having to use the client itself.
While working with the MQTT client on the browser, I noticed callbacks (sent through setImmediate) are missing parameters. I tracked the problem down to this snippet: ```javascript const setImmediate =...
In a browser, where the `setImmediate` and `nextTick` polyfills are needed, the Errors being passed such as [this scenario](https://github.com/mqttjs/MQTT.js/blob/3451564363cf0933355ab6d66e73c80fa13379e8/lib/client.js#L726) are ignored. Issue was originally raised [here](https://github.com/mqttjs/MQTT.js/issues/1474).
### Summary The documentation of the events emitted by the VrpcRemote seems to: - deviate from the actual behaviour of the VrpcRemote - be a bit unclear as to how...
This PR corrects the type definition on typescript to reflect the actual behaviour of the task  that returns the given config and not a void.
This PR introduces the ability to configure nyc through environment variables, requiring the maintenance of one less configuration file. Such as: `NYC_CONFIG="{\"report-dir\":\"coverage/cypress\",\"temp-dir\":\"coverage/temp\"}" npm run your:testing:task`