-
Notifications
You must be signed in to change notification settings - Fork 33
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
V2.8.0 Introduces incompatibilities with web and react native #151
Comments
Yep same issue for me with React Native / Expo:
Reverting to |
I'm still facing the same error even though reverting to |
How annoying @bgarcia95 ! FWIW even after getting it working I ended up reverting to just |
It seems like this code might be causing issues. Let's replace it with an alternative solution. |
@bgarcia95 @vonkanehoffen fixed on |
Describe the bug
When running the app in react-native, I get the following error
I believe this is occurring because
path
is a node specific library, and it is being used in a non-node context. I haven't validated that this doesn't work in web, but I imagine it wouldn't sincepath
is also not part of the standard library in web.This appears to have been introduced in #149
To Reproduce
Steps to reproduce the behavior:
Expected behavior
For it to work
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: