-
Notifications
You must be signed in to change notification settings - Fork 161
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
Is there anyway to get this to work in the Next.js edge environment? #215
Comments
Judging by the restrictions listed here: https://nextjs.org/docs/api-reference/edge-runtime#unsupported-apis it would probably take a ton of work to make this lib usable in that environment (no |
Yes, I think you're right. I just fell back to the default Next serverless environment. |
As an alternative, you can just call via mixpanel's HTTP API using fetch in the edge. |
looking for same. If it's too much work, would be easier for you guys to port |
That seems like it would also be a big project, since the browser lib relies on a lot of browser APIs to function correctly. |
On init, it throws an error
Error: The edge runtime does not support Node.js 'http' module.
The text was updated successfully, but these errors were encountered: