Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
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 failure hit both upgraded projects and fresh Next.js 15 apps with only chargebee installed.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Fixed in chargebee v3.12.0 (the fix landed first in the 3.12.0-beta.1); upgrade to v3.12.0 or newer. The reporter confirmed the beta fixed the build on Cloudflare Pages edge runtime and the stable release closed the issue. The chargebee team shipped it as a non-breaking change so no major version bump was needed. Source: https://github.com/chargebee/chargebee-node/issues/68
Source: https://github.com/chargebee/chargebee-node/issues/68
Fixes the chargebee Node SDK failing with 'Can't resolve http' after upgrading to Next.js 15.
Shows how to fix can't resolve 'expo-secure-store' with Kinde Next.js SDK (fixed in 2.8.1). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix broadcastChannel Channel is closed errors after upgrading okta-auth-js to 6.4.0 (fixed in 6.7). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.