infrastructure-package-exports-err-package-path-not-exported-when-importing-an-es-5b7e702d

THEN Update the package.json of the SDK to include a proper 'exports' field that defines separate entry points for ESM and CJS consumers, ensuring the main entry point is accessible. This resolves module resolution errors for both module systems.

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