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

[Node 4] Prepare for Node 4 #2545

Closed
4 of 5 tasks
ide opened this issue Sep 3, 2015 · 12 comments
Closed
4 of 5 tasks

[Node 4] Prepare for Node 4 #2545

ide opened this issue Sep 3, 2015 · 12 comments
Assignees
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@ide
Copy link
Contributor

ide commented Sep 3, 2015

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

@ide ide self-assigned this Sep 3, 2015
@cpojer
Copy link
Contributor

cpojer commented Sep 3, 2015

  • Does it have arrow functions like Chrome 45?
  • Where can I find the RC?

@ide
Copy link
Contributor Author

ide commented Sep 3, 2015

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).

@cpojer
Copy link
Contributor

cpojer commented Sep 3, 2015

They are now shipped natively in Chrome, and they are awesome.

@vjeux
Copy link
Contributor

vjeux commented Sep 4, 2015

Me gusta

@ide ide changed the title Prepare for Node 4 [Node 4] Prepare for Node 4 Sep 5, 2015
@ide
Copy link
Contributor Author

ide commented Sep 5, 2015

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:

 FAIL  Libraries/Utilities/__tests__/MessageQueue-test.js
SyntaxError: react-native/Libraries/Utilities/__tests__/MessageQueue-test.js: react-native/Libraries/Utilities/MessageQueue.js: react-native/Libraries/JavaScriptAppEngine/System/JSTimers/JSTimersExecution.js: Unexpected identifier
  at Function (native)
  at makeComponent (react-native/node_modules/jest-cli/src/lib/moduleMocker.js:157:15)
  at generateMock (react-native/node_modules/jest-cli/src/lib/moduleMocker.js:222:16)
  at Object.generateFromMetadata (react-native/node_modules/jest-cli/src/lib/moduleMocker.js:255:14)

jest bug opened here: jestjs/jest#488. react-native tests pass with jestjs/jest#489.

@cpojer
Copy link
Contributor

cpojer commented Sep 5, 2015

👍 I have a reasonably important bug to fix for jest, I'll do that on Tuesday and tag 0.5.2.

@ide
Copy link
Contributor Author

ide commented Sep 8, 2015

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

@brentvatne
Copy link
Collaborator

@ide 😍

@alinz
Copy link

alinz commented Sep 9, 2015

👍

2 similar comments
@cyprusglobe
Copy link

👍

@brunoksato
Copy link

+1

@chirag04
Copy link
Contributor

Seems like everything is in place for node 4 now.

@facebook facebook locked as resolved and limited conversation to collaborators Jul 21, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 21, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

9 participants