feat!: Added support for ECMAScript Modules (ESM) #338
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: Requires Node version >= 12
This library's coding causes issues with tools like esbuild and vite due to the way it relies on dynamic
require()
statements. I'm proposing a shift to dynamic imports to introduce support for ES Modules.The bulk of the changes move imports like this:
to this:
Where
use()
is a utility function that handles import, caching, and additional options, and returns a promise.Besides bundling a shim for
Promise.any()
, this runs native. We could consider including more polyfills or building with Babel to support older Node versions. This supersedes #294.