Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Using @kinde-oss/kinde-auth-nextjs in an Expo/React Native context failed with Can't resolve 'expo-secure-store'. The SDK pulled in the Expo secure storage module unconditionally, so bundlers without Expo could not resolve it. The import chain broke the build even though the app never used Expo features directly.
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 @kinde-oss/kinde-auth-nextjs 2.8.1; upgrade to 2.8.1 or newer. A maintainer confirmed the fix and a reporter verified it works. The fix removed the unconditional import so non-Expo bundlers no longer try to resolve the Expo module. Source: https://github.com/kinde-oss/kinde-auth-nextjs/issues/347
Source: https://github.com/kinde-oss/kinde-auth-nextjs/issues/347
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.
Fixes the chargebee Node SDK failing with 'Can't resolve http' after upgrading to Next.js 15.
Shows how to fix notion SDK breaks Next.js 13 Vercel build: Module not found: Can't resolve 'encoding'. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.