-
Notifications
You must be signed in to change notification settings - Fork 173
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
Error on build #22
Comments
Sorry, we need to put |
any idea of when this can be fixed? |
For a temporary fix for this issue in your React Native project, you actually want to run the command More information here https://github.com/skevy/babel-preset-react-native-stage-0. |
What is the preferred approach here? I was given the suggestion to not compile out a lib folder from the src directory, but I'm really not sure how to support the community without doing so. Should I remove the |
See release v0.2.3 on NPM, |
Thanks @niftylettuce and @slayrbear ! |
@niftylettuce I have the v0.2.3 and react-native v0.28.0 and same error. |
@slayrbear It works for me. |
Very weird. It was working for me, now it's not. @deju Can you confirm if this is working for you once more? Make sure you restart the package manager, etc and try again. @niftylettuce Any ideas to permanently fix this? My commit should have gotten the error fix by adding babel-preset-react-native-stage-0 as a dev dependency to the package. Anyways, the temporary fix I mentioned earlier in this thread will fix this in your RN project. |
Some news? |
I am getting the same error. |
@faizan-tariq-confiz i think this will solve your problem. |
I have already tried this, and its not working |
+1 |
I did @slayrbear response and fixed it:
|
Hi there, Regards |
Taking a look here.. |
See release v0.3.0, install with |
I just tested this out on latest version of React Native and also took this screenshot showing this is now working as of |
Hi. I am getting this error, which seems related to #20
I am using react native 0.28.0, and react-native-loading-spinner-overlay 0.2.2.
Apparently the fix for #20 did not work for me. Am I doing something wrong?
The text was updated successfully, but these errors were encountered: