Closed hxtruong6 closed 4 months ago
This is an ESM package and cannot be required, that's why there's no require
. Also I'm 99% sure it wouldn't fix your issue with module resolution either since the old Node10
resolution scheme doesn't look at this at all.
This pull request adds the 'require' field to the
exports
option in thepackage.json
file. This change is intended to solve issues with CommonJS module resolution when using TypeScript withtsconfig.json
configured to use"module": "commonjs"
.package.json
to include therequire
field in theexports
section for both the main entry point and the./keys
subpath.