Change some exports to move towards more ESM compatibility

[danielholmes]

What's Changing and Why

There's some parts of the source code that still use commonJS export style. This change makes a more consistent code base and once completely done, open opportunities to simplify and improve the compile steps (babel, browserify, etc).

Note: There are still 1 locations with CJS exports, one i being handled in another PR, the other is the core requests module which requires a larger discussion (PR forthcoming).

What else might be affected

It's a pretty simple change. The tests run for me and I can't imagine it breaking anything

Tasks

• Add tests
• Update Documentation
• Update jimp.d.ts
• Add SemVer Label

[hipstersmoothie]

Hmm I don't know what the actions aren't running

[danielholmes]

@hipstersmoothie I found some discussion about this in the actions/checkout repo:

actions/checkout#298

One suggested fix is:

token: ${{ secrets.MY_TOKEN || github.token }}

in the workflow

[hipstersmoothie]

ah. I'm not sure that line was necessary. If it is thanks for the heads up!

[hipstersmoothie]

These other failures are for the canary release. I want to make running that part something I can opt into via label or something. So for now it will only work for people with access to the repo

[github-actions]

🚀 PR was released in v0.21.3 🚀