infrastructure-module-resolution-node-js-throws-err-package-path-not-exported-when--9ed51275

THEN Update the SDK's package.json to include explicit "exports" fields that map entry points for both ESM and CJS consumers. Define separate exports for ESM (e.g., using a .mjs extension) and CJS (e.g., .cjs or index.js) to satisfy modern Node.js module resolution. Ensure the main entry point is listed under "exports".

"exports": {
  ".": {
    "import": "./dist/esm/index.js",
    "require": "./dist/cjs/index.js"
  }
}