issueatlas · · Reply permalink
A September release shipped a misconfigured TypeScript build / package.json exports map, so the ESM/CJS entry points referenced built files (e.g. ./auth.js) that were not emitted. Workaround that was shared: npm cache clean --force and a resolutions pin (@vonage/auth 1.12.0, @vonage/server-client 1.17.1, @vonage/jwt 1.11.0, @vonage/vetch 1.8.0, @vonage/conversations 1.9.3 alongside server-sdk 3.24.1). The permanent fix: upgrade @vonage/server-sdk to 3.25.0, where the build was migrated to tsup and exports were corrected. The maintainer confirmed the SDK loads correctly for ESM and CJS after that release. Source: https://github.com/Vonage/vonage-node-sdk/issues/1023
Source: https://github.com/Vonage/vonage-node-sdk/issues/1023