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 doesn't support newest Node (12.11.1) #26808

Closed
Coruscate5 opened this issue Oct 10, 2019 · 10 comments
Closed

React Native doesn't support newest Node (12.11.1) #26808

Coruscate5 opened this issue Oct 10, 2019 · 10 comments
Labels
Bug Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@Coruscate5
Copy link

React Native version: 0.61
(System:
OS: Windows 10
CPU: (16) x64 Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
Memory: 10.17 GB / 31.91 GB
Binaries:
Node: 12.11.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.17.3 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.11.3 - C:\Users\SOMEONE\AppData\Roaming\npm\npm.CMD
SDKs:
Android SDK:
API Levels: 19, 21, 22, 23, 24, 27, 28, 29
Build Tools: 19.1.0, 21.1.2, 22.0.1, 23.0.1, 23.0.2, 23.0.3, 27.0.3, 28.0.3, 29.0.2
System Images: android-19 | ARM EABI v7a, android-19 | Intel x86 Atom, android-23 | Google APIs ARM EABI v7a, android-23 | Google APIs Intel x86 Atom, android-24 | Android TV Intel x86 Atom, android-24 | Android Wear ARM EABI v7a, android-24 | Android Wear Intel x86 Atom, android-24 | ARM 64 v8a, android-24 | ARM EABI v7a, android-24 | Intel x86 Atom, android-24 | Intel x86 Atom_64, android-28 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom
Android NDK: 17.1.4828580
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.2 => 0.61.2)

Steps To Reproduce

  1. Follow "Getting Started" guide to install latest Node version
  2. Attempt to run "react-native run-android" on Windows using Emulator or physical device
  3. Fails

Describe what you expected to happen:
Sample app works

Snack, code example, screenshot, or link to a repository:
Related issue here was closed prematurely by author: #26598

@EnduIf
Copy link

EnduIf commented Oct 20, 2019

After some investigation i found the bug and already created a pull request for the Metro Bundler
facebook/metro#464
hopefully this gets accepted soon.

@stale
Copy link

stale bot commented Jan 19, 2020

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Jan 19, 2020
@gluons
Copy link

gluons commented Jan 19, 2020

Is it fixed? Can I safely upgrade my Node to 12?

@stale stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Jan 19, 2020
@stale
Copy link

stale bot commented Apr 18, 2020

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Apr 18, 2020
@gluons
Copy link

gluons commented Apr 18, 2020

Is it clearly fixed? @Stale

@stale stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Apr 18, 2020
@oleksandr-dziuban
Copy link

@gluons @NyauIf
Just update metro-react-native-babel-preset to latest 0.59.0 version and issue will be fixed.
I'm on latest NodeJS 12.18.0 and react-native 0.62.2

@stale
Copy link

stale bot commented Sep 11, 2020

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Sep 11, 2020
@gnprice
Copy link
Contributor

gnprice commented Sep 11, 2020

I believe this has been fixed and can be closed.

In addition to @oleksandr-dziuban 's report above: our project has been using Node 12 for some time, with RN v0.61.5, and we've seen no sign of problems related to the Node version.

@stale stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Sep 11, 2020
@stale
Copy link

stale bot commented Dec 25, 2020

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Dec 25, 2020
@github-actions
Copy link

This issue was closed because it has been stalled for 7 days with no activity.

@facebook facebook locked as resolved and limited conversation to collaborators Mar 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

5 participants