Hey py110, thanks for reporting this issue!

React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.

• If you don't know how to do something or something is not working as you expect but not sure it's a bug, please ask on StackOverflow with the tag react-native or for more real time interactions, ask on Discord in the #react-native channel.
• If this is a feature request or a bug that you would like to be fixed, please report it on Product Pains. It has a ranking feature that lets us focus on the most important issues the community is experiencing.
• We welcome clear issues and PRs that are ready for in-depth discussion. Please provide screenshots where appropriate and always mention the version of React Native you're using. Thank you for your contributions!

i have same issue too, even in a new project created by react-native init

+1

rm ./node_modules/react-native/node_modules/react-transform-hmr/node_modules/react-proxy/node_modules/react-deep-force-update/.babelrc I remove this file, then work

@py110 maybe you can have a try

@carlos-wong +1

+1

+1

This root cause of the issue is that React Native uses Babel 6, which deprecated the use of the stage option on .babelrc files, and react-deep-force-update, a sub-dependency of React Native, still declares a .babelrc file with that option.

This is an issue with any third party modules that still use an older Babel in their own build process and do not clear the configuration files for the npm publish.

I have worked around the issue by adding the following npm run scripts to my package json:

  "scripts": {
    "clean:babelrc": "find ./node_modules -name react-packager -prune -o -name '.babelrc' -print | xargs rm -f",
    "postinstall": "npm run clean:babelrc"
  }

The script nukes all .babelrc files under the node_modules directory after every npm install, except the one under the react-packager directory, which is React Native packager uses to configure its own babel rules.

Note that this issue has been raised on Stack Overflow by a couple of users, in addition to the reports here:

• http://stackoverflow.com/questions/34975286/reactnativecli-init-helloworld-project-build-error-with-babel-transformerror
• http://stackoverflow.com/questions/34967261/when-i-learn-the-first-react-native-demo-react-native-error

I have not experienced this error myself (not on 0.18 in any of my apps yet), but it appears the depency tree that causes this error is the following:

• react-native depends on react-transform-hmr
• react-transform-hmr depends on react-proxy
• react-proxy depends on react-deep-force-update
• react-deep-force-update contains the offending .babelrc file

The downstream dependencies below react-transform-hmr have since been updated to use Babel 6, but the latest react-transform-hmr still depends on react-proxy@1.1.1. We would need to upgrade the html library to the latest react-proxy@1.1.2 to resolve this issue.

I have opened an issue gaearon/react-transform-hmr#55 at react-transform-hmr to see if we can get this upgraded.

+1

+1

+1