Closed tbnritzdoge closed 3 years ago
This is an unnecessary code quality sacrifice when we can simply adjust our build settings. You can set the target to either ES2018 or Node12 in our ESBuild config to resolve this more effectively without needing to sacrifice developer experience.
:tada: This PR is included in version 1.3.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Coverage remained the same at 98.627% when pulling 155885686dccb4f1c11567ee4d9f4797d009c919 on fix/work-on-older-node into f869666169a39c5f0baacc48d23b48c6a6073163 on master.