Closed c43721 closed 3 years ago
Default export in an ECMAScript2017+ context makes sense. This module was originally written in 2018 in plain JS, and export = RCON
was the normal convention 🤷♂️.
This is a very welcome change. Thanks, @c43721.
Release v.2.0.1 has been published to NPM including changes in this PR.
Awesome! I'll change over my backend to use this package now.
Reason for this change is because of the following:
However, if we use the alternative syntax to import everything as a constant:
Changes:
With the default export, everything works as expected.