Caylan

@Nokel81, I am in the process of testing your patch on Windows, but heads up that your work breaks builds on macOS. Here's what I'm seeing: ``` An unhandled error...

@Nokel81, I had a windows user test my app's build with your PR and it worked. So that's good news! I'm not in a good position to modify this codebase,...

@Nokel81, did you see the latest comment over at native-reg? He's modified the gypfile to minimize complexity with bundling/packaging. https://github.com/simonbuchan/native-reg/issues/23#issuecomment-888821548 ``` Give this a try in @next tag / 0.3.6...

Any progress on this? Any work-arounds?

Is there a way to fully disable this mode all together? Entering a very large number works, but isn't ideal. I'll open a new issue if requested. Values of zero,...

Thank you for the great project. 1. What kind of app are you making? (Optional) I've built http://label.live with many, many of native modules: usb (on Mac and windows!), fonts,...

This command can be used to generate the error: ``` $ react-native bundle --platform ios --entry-file index.js --bundle-output ./ios/main.jsbundle Loading dependency graph, done. node_modules/react-native/Libraries/Components/RefreshControl/RefreshControl.js: Property value expected type of string...

This seems to be related to flow-runtime lacking babel 7 support https://github.com/codemix/flow-runtime/issues/184. Fwiw, "babel-types" is babel version 6. Perhaps that is causing the underlying issue. I've since removed flow-runtime support...

This is turning out to be a very interesting error and possibly a bug. I distilled the issue down to this failing test: ``` export const input = ` //...

I have posted a similar issue here: https://github.com/codemix/flow-runtime/issues/216