Browser build is used in CF workers environment

Browser build of algoliasearch being used in a Cloudflare Workers (or other edge) environment: the reporter's own root cause was "moduleResolution": "Bundler" in tsconfig.json resolving the wrong build. Changing moduleResolution fixed it on their end. If you hit XMLHttpRequest-is-not-defined style errors in a non-browser runtime, check your tsconfig moduleResolution first.

Source: gh:algolia/algoliasearch-client-javascript#1548 (Algolia)

In gh:algolia/algoliasearch-client-javascript#1548, the issue was: ### Description After migrating from v4 to v5 (which was confusing in itself, as others have mentioned), I'm encountering weird issues with the algolia client in production. Such as: `algolia.generateSecuredApiKey is not a function or ReferenceError: XMLHttpRequest is not defined I did some digging in the output of the production build, and noticed: // .wrangler/tmp/chunks/_/algolia.mjs function algoliasearch(appId, apiKey, options) { return { ...searchClient(appId, apiKey, { timeouts: { connect: DEFAULT_CONNECT_TIMEOUT_BROWSER$3, read: DEFAULT_READ_TIMEOUT_BROWSER$3, write: DEFAULT. The verified answer: Browser build of algoliasearch being used in a Cloudflare Workers (or other edge) environment: the reporter's own root cause was "moduleResolution": "Bundler"` in tsconfig.json resolving the wrong build. Changing moduleResolution fixed it on their end. If you hit XMLHttpRequest-is-not-defined style errors in a non-browser runtime, check your tsconfig moduleResolution first.. Issue URL: https://github.com/algolia/algoliasearch-client-javascript/issues/1548