-
Notifications
You must be signed in to change notification settings - Fork 46
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
Add support for react-native-web #276
Comments
Hi @onlyanegg, thanks for reaching out on this topic! It is in our backlog, but it isn't places on the roadmap yet. |
Ok, thank you :) |
+1 on this I've been using a custom cross-platform abstraction -- and I'm very glad to have the functionality I am able (thanks!) But I will say that it's been quite difficult at times, to keep things in aligned After a couple bugs slipped in, I've started to ensure that any update includes an exhaustive accounting of configuration changes / types def updates to ensure consistency between the platforms. Even if a fully fledged solution doesn't make it onto the roadmap this time around, it would be tremendously useful to start aligning the APIs. API Mismatch SummaryNative- vs web-specific config
Overlapping config
Misc Other Issues
|
Hey, @leggomuhgreggo! Would you be open to sharing your abstraction? That could be super useful for me (and maybe others?) at least as a reference. |
@onlyanegg the abstraction is a library in a private monorepo, but I threw the raw code in a repo here. |
Thanks, @leggomuhgreggo! |
Updated the example x-platform RUM client repo |
Hey, @louiszawadzki! I just wanted to bump this. I'm having to do a bit of a refactor to our implementation because of and Expo update. Has supporting web in this lib gained any traction? |
Is your feature request related to a problem? Please describe.
The react-native-web build does not work
Describe the solution you'd like
Support react-native-web
Describe alternatives you've considered
Currently I'm mocking DdSdk and other objects in the web build with a webpack alias. I could try writing code to make requests either with the browser SDK or an http client. But it think it would make more sense if it lived in here, even if it were basically a proxy to the browser SDK.
The text was updated successfully, but these errors were encountered: