Skip to content
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

React Native Integration #205

Open
2 of 10 tasks
prasanth95 opened this issue May 25, 2018 · 1 comment
Open
2 of 10 tasks

React Native Integration #205

prasanth95 opened this issue May 25, 2018 · 1 comment

Comments

@prasanth95
Copy link

prasanth95 commented May 25, 2018

This is a:

  • Bug Report
  • Feature Request
  • Question
  • Other

Which concerns:

  • flow-runtime
  • babel-plugin-flow-runtime
  • flow-runtime-validators
  • flow-runtime-mobx
  • flow-config-parser
  • The documentation website

What is the current behaviour?

flow-runtime: Failed to reveal unknown type in Temporal Dead Zone

Failed to print error: Requiring module "NativeModules", which threw an exception: RuntimeTypeError: config[3] must be an Array

Expected: Array

Actual Value: undefined

Actual Type: void

config[4] must be an Array

Expected: Array

Actual Value: undefined

Actual Type: void


What is the expected behaviour?

Flow runtime should be integrated


Which package versions are you using?

"react-native": "0.51.0",
"flow-runtime": "0.17.0",
"babel-plugin-flow-runtime": "0.17.0"

.babelrc config

{
  "presets": ["react-native", "flow"],
  "env": {
    "development": {
      "plugins": [
        ["flow-react-proptypes", { "ignoreNodeModules": true }]
      ]
    },
    "production": {
      "plugins": ["ignite-ignore-reactotron"]
    }
  },
  "plugins": [
    ["flow-runtime", {
      "assert": true,
      "annotate": true
    }],
    "transform-decorators-legacy",
    "transform-class-properties",
    [
      "module-resolver",
      {
        "root": ["./app"],
        "extensions": [".js", ".ios.js", ".android.js"]
      }
    ]
  ]
}
@mfpiccolo
Copy link

I am getting this same error and have yet to fine a work around which is a shame because it was previously working exactly how I wanted it to. @prasanth95 did you find a way to make it work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants