-
Notifications
You must be signed in to change notification settings - Fork 19
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
The eslintrc should be overhauled for explicit Node v4 support #93
Comments
We need to use the same configure as react-native. We already merged rnpm into RN core, so I don't see a point of changing RNPM repo now. I think you'll be able to use some commands in the next release already 😉 |
Respectfully I disagree. If all the JS code for P.S. Very excited about |
Well, I think you're mostly correct. The only thing is that react-native requires node v4+ as well, so I though mb it can fit for rnpm too, because we don't want to introduce yet another code style in subfolder |
I agree about the code style, that's why I think the |
Ok, sounds reasonable 👍 |
It's currently set to use
babel-eslint
, which is allowing destructuring and other features that Node v4 (and even v5) do not support.The text was updated successfully, but these errors were encountered: