-
Notifications
You must be signed in to change notification settings - Fork 38
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
Browser Support for JS SDK #18
Comments
Yes we should be supporting both. I'll take a look at this. Thank you for bringing it up. |
Thank you @dmoss18. Looks like this was introduced in |
@osdevisnot I have a branch up here. Try it and lmk if it helps. |
It helps; but I think we might need to find a better solution to browser vs node compatibility scene. For eg: the try catch approach in #24 still results in warnings as noted #24 (review); mainly because we still import |
@osdevisnot I have merged PRs for the issues you mentioned. Please confirm that this issue is resolved and I will close and publish a new version of the package. |
This issue is fixed. However I forgot to add one change which should really be part of #19. I will create a separate PR for that soon. |
I am attempting to use the SDK client in browser environment. However, this results in below errors:
Can we please author this SDK in a manner that is compatible with both node.js and browser?
If the is willing to support this feature, I can even attempt to submit a PR to that effect.
The text was updated successfully, but these errors were encountered: