feat: sync main w/ beta

[rolandjitsu]

What kind of change does this PR introduce?

• Bug Fix
• Feature
• Refactoring
• Style
• Build
• Chore
• Documentation
• CI

Did you add tests for your changes?

• Yes, my code is well tested
• Not relevant

If relevant, did you update the documentation?

• Yes, I've updated the documentation
• Not relevant

Summary

This PR will get all the changes from beta to main and trigger a major release.

Does this PR introduce a breaking change?

Yes, there are a few breaking changes:

1. The min required node version will be 18
2. CommonJS is no longer supported

Other information

[jonkoops]

Looks like this contains some breaking changes, so let's not merge this until we are sure we want to do a major release.

[rolandjitsu]

Looks like this contains some breaking changes, so let's not merge this until we are sure we want to do a major release.

Yeah, it needs a rebase. But that will mess up semantic-release as we discussed in file-selector.

[jonkoops]

I think what we can do is backport fixes from master to beta and then swap the branches when we decide to release so:

• master becomes 2.x
• beta becomes the new master

That way we don't have to deal with a nasty merge/rebase