-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
There is a compatibility problem with react-native-web in expo. #3231
Comments
Can confirm the error on 2.13.13. Someone said here APSL/react-native-keyboard-aware-scroll-view#448 downgrading to 2.13.12 fixed the issue. |
Anyone coming here looking for a solution, check this out: https://forums.expo.io/t/expo-start-web-failed-to-compile-after-import-native-base/40826/9 |
Any news on this? It's a big problem for me, stopping me getting a web build out. I have to run on 2.13.8, and on that version there are plenty of other bugs still present. |
Confirmed, not sure how to fix it though now :/ |
Same Issue :( |
It seems they are already working on this issue: #3264 (comment) |
throws error GeekyAnts/NativeBase#3231
Has anyone found a temporary fix yet? |
@EdinK1, I just forked it and fixed the issue there, until they release a new version with the fix. |
@matias91 Can you expand more on how to fix it as I don't understand how to solve it. Thanks! |
Sure, @EdinK1. That depends on the error you are receiving. Let me know if you have doubts. Hope this help. |
This is the problem I have @matias91 |
Okay, @EdinK1. I'm using expo, and that answer worked for me, but I don't know your tech stack. |
Hey @matias91, So, I went ahead did everything the forum told me and now I'm getting a different error.
This is where I am stuck. Let me know if you know a way around it. Thank you! |
@EdinK1, that's what I explained you here: #3231 (comment) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
A note for anyone else using expo web and looking for workaround to the @matias91 mentioned workaround https://forums.expo.io/t/expo-start-web-failed-to-compile-after-import-native-base/40826/9, but I think there's a simpler solution if you didn't already need to customize your webpack. {
"expo": {
"web": {
"build": {
"babel": {
"include": ["@codler/react-native-keyboard-aware-scroll-view"]
}
}
}
}
} This made the However I should note that as of this date that just leads to the next problem with native-base and expo web, #3280, which is not currently merged. It has had activity in the past week so that may happen soon, or you can see that discussion for some possible workarounds if you need solutions before it gets merged. |
This is the problem I have too. Finally, how to solve it |
I've this error |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
"react-native-web": "^0.13.9",
"native-base": "^2.13.14",
"expo": "~38.0.8",
"react-native-keyboard-aware-scroll-view": "^0.9.2",
There is a compatibility problem with native-base and react-native-web.
With the yarn web included in expo,
I used the code below.
code-------------------------------
yarn web
The following error occurs
error-----------------------------------------
=> Temporarily modified through the forum..
=> Source: https://forums.expo.io/t/expo-start-web-failed-to-compile-after-import-native-base/40826
make sure you have react-native-keyboard-aware-scroll-view folder in your node_modules folder, not inside any other folder
go to native base/dist/src/basic and open Content.js
var _reactNativeKeyboardAwareScrollView=require('@codler/react-native-keyboard-aware-scroll-view')
var _reactNativeKeyboardAwareScrollView=require('react-native-keyboard-aware-scroll-view')
=> However, another error occurs.
error------------------------------------------------
No more work.
I wish you a quick solution.
I love the web and native-base that I use with expo.
The text was updated successfully, but these errors were encountered: