The package throws MODULE_NOT_FOUND error when trying to import it in an ES module project. The issue is in package.json — the "exports" field points to "./dist/esm/index.js" for the ESM entry point, but inside the published package, the actual file is named "./dist/esm/index.mjs". The package.json configuration is wrong; it does not match the actual file structure of the published npm package. The source of the error is the package author's misconfiguration.
The package throws MODULE_NOT_FOUND error when trying to import it in an ES module project. The issue is in package.json — the "exports" field points to "./dist/esm/index.js" for the ESM entry point, but inside the published package, the actual file is named "./dist/esm/index.mjs". The package.json configuration is wrong; it does not match the actual file structure of the published npm package. The source of the error is the package author's misconfiguration.