-
-
Notifications
You must be signed in to change notification settings - Fork 325
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
Build breaking with yarn v0.24.6 on OSX (running web + native) #217
Comments
If yarn adds a way to change the Python version being used this will be fixed as building with Python 2.7 instead of Python 3 fixes this issue. Ref: yarnpkg/yarn#3519 |
Seem like |
Yes, working for me now too. And I have faced this bug previously. Not sure what has changed, but it works now. Closing this issue. |
@mairh Doesn't reproduces for me now |
@Vlasenko Are you using the same Could you try the following options (if you haven't done already)
|
Yes, I'm using the yarn |
Although, it shouldn't make any difference, but could be it only be happening on |
@mitjade When you have time could you give it a try? |
@mairh Will do in a few hours. |
Currently it's working for me. I had some problems with yarn when I was running also iOS simulator. For web only no problems so far. |
yes, for the web only it works fine. I'll keep this issue open for a short while and see if the yarn problem is just hit and trail or something else. Thanks for checking it out though. |
@mairh this issue is because of bunyan it won't just randomly go away you'll need to either switch to using npm install for now with python 2.7 set or wait for yarn to add a python flag as I stated above. Bunyan issue: trentm/node-bunyan#216 |
This should be fixed now via: It utilizes latest
|
This is just a heads up that the build is breaking when running
yarn watch
usingv0.24.6
Failing with error
It seems like this is a common issue
trentm/node-bunyan#216
expo/create-react-native-app#135
Workaround is to use
npm install
andnpm run watch
instead ofyarn
andyarn watch
The text was updated successfully, but these errors were encountered: