Typescript migration build issues esm

[drewbrokke]

Description

Continuing work on #492

This pull converts the project to ESM. This is only necessary because the new versions of certain dependencies require an ESM project, in this case update-notifier.

As noted in the message of the first commit (91d92b9 at the time of this writing), I followed the process detailed here: https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c.

More specifically, I tracked with these headers:

• How can I move my CommonJS project to ESM?
• How can I make my TypeScript project output ESM?
• How can I import JSON?

It was a super helpful guide and I learned a lot in the process. It's worth looking over and reading the linked articles whenever you have a chance.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist:

• I have read the CONTRIBUTING document.
• My commits follow the commitizen commit convention
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[jwu910]

Thanks drew! initial testing looks great 🥲