Closed astephens25 closed 2 years ago
Hmm, there are a few other things wrong with the esm
build. I will release a fix soon. Thanks for reporting.
You are welcome. If I can assist in any way, please let me know. Otherwise I will watch out for the update.
@astephens25 Please give better-ajv-errors@1.1.2
a try. It should be fixed now.
It appears to be working. I have not checked it directly, but a member of my team was able to update to the latest and the project appears to be working. Thanks so much for that.
I am unable to use better-ajv-errors >= 1.0.0 from an ESM project. I have attempted the import on Node 12 and 16 and both fail in the same manner. I checked and the "type" property is not set in the package.json which causes the initial error, but even when set, the import fails due to the lack of file extensions on the imports in the "esm" directory of the module.
I use ESM import exclusively in the project I am working on and have not encountered this with another NPM Module.