-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
[Node 4] Prepare for Node 4 #2545
Comments
|
The RC is potentially getting cut later today. If the V8 4.5 upgrade lands in time, then I believe it includes arrow functions (that aren't broken and behind a flag like in 3.x). |
They are now shipped natively in Chrome, and they are awesome. |
Me gusta |
Some good news: react-native installs fine with 4.0.0-rc.1. The packager, Chrome debugger, and React devtools all work with the UIExplorer. All of the jest tests pass except this one:
jest bug opened here: jestjs/jest#488. react-native tests pass with jestjs/jest#489. |
👍 I have a reasonably important bug to fix for jest, I'll do that on Tuesday and tag 0.5.2. |
All tests are green! https://travis-ci.org/facebook/react-native/builds/79353110 @vjeux could you find someone to look at #2548 (upgrade jest + travis), #2547 (add message to the packager), and #2546 (update docs) in that order? Once #2548 is in, we can also cherry-pick 7f65971 over to 0.11-stable and ship Node 4.x support with 0.11 and not think about "io.js" any more. EDIT: I went ahead with cherry-picking 7f65971 |
@ide 😍 |
👍 |
2 similar comments
👍 |
+1 |
Seems like everything is in place for node 4 now. |
I believe the codebase is in good shape for Node 4.0. It's going to be much better when we can tell people just to get the latest version of Node without any of the io.js confusion.
Things that need to be done:
cc @vjeux and @cpojer I think you will be excited
The text was updated successfully, but these errors were encountered: