Open stevengum opened 3 years ago
Things to consider: updating eslint rules, listening for process.on('unhandledRejection')
in the tests, and failing if emitted.
I encountered unhandled rejections when the callbackUrl of a request to a bot included a URL that could not be resolved (that resulted in getaddrinfo ENOTFOUND). I tried to reproduce it so I could provide more details but no luck. I will update here if I manage to reproduce it.
The error was: new RestError (/app/node_modules/botframework-connector/node_modules/@azure/ms-rest-js/dist/msRest.node.js
We should rewrite the existing JS samples to have proper rejection handling. Perhaps follow the pattern set via https://github.com/microsoft/botbuilder-js/pull/3492
Official Node 15 blog post
Snippet from blog post:
While the SDK doesn't officially support odd number versions of Node (aka non-LTS), addressing unhandled rejections will: