library · inferred from evidence
http
A Node.js core module that the chargebee SDK attempted to import, causing the resolution error in Next.js 15.
- Could not resolve crypto, http, https using @workos-inc/node on Cloudflare Pages
Adding the @workos-inc/node SDK to a Cloudflare Pages project failed at build/dev time with Could not resolve "crypto", "http", "https": the package "crypto" wasn't found on the file system but is built into node. The errors came from the S
- chargebee: Can't resolve 'http' after upgrading to Next.js 15 (fixed in v3.12.0)
After upgrading a project from Next.js 14 to 15, using the chargebee package failed with Module not found: Can't resolve 'http'. The SDK imported Node.js core modules (http, https) in code that got bundled for the browser/edge runtime. The
- React Native: Unable to resolve module http from @algolia/requester-node-http (algoliasearch v5)
With `algoliasearch` 5.4.3 and React Native 0.73.6, the Metro bundler fails with `Unable to resolve module http from node_modules/@algolia/requester-node-http/src/createHttpRequester.ts` because that module imports Node's `http`, `https`, a