-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReferenceError: Cannot access 'isBrowser' before initialization #346
Comments
Having the same issue using Next 15.1.2 |
The SDK remains untested and (it looks) incompatible with some new features of Next.js 15. For now, you can downgrade to Next.js 14, or you can connect to Deepgram via a |
thanks, how do you "connect to Deepgram via a pages/api express-like proxy instead of using the SDK in Next.js specifically" ? is there an example of that? |
Following this. I have, for now, delegated the work to a Python lambda and called the lambda within my Next API route. Alternatively, one may call the backend API directly (cURL). I believe it is also related to webpack, see webpack/webpack#12724. To confirm, could you share your Next config file and tsconfig files? I'm also experiencing the same issue, here are mine:
And
|
Any updates on this? |
As they replied in related issue, current SDK is not compatible with Next.js 15 and offer to downgrade |
What is the current behavior?
I am trying to use the JS sdk in a Next.js 15 App Router api route. So executed on the server.
I am instantiating Deepgram as per instructions here with
but I get the following error:
Steps to reproduce
const deepgram = createClient(process.env.DEEPGRAM_API_KEY);
Expected behavior
To just be able to use the sdk in an api route
Please tell us about your environment
Other information
This is the stack trace:
The text was updated successfully, but these errors were encountered: