[FIXED] Unable to create new RN 0.72 project with Node 16 again #40797

Activity

1. jonthysell

   added

   Needs: Triage 🔍

   on Oct 11, 2023
2. facebook-github-bot

   added

   p: MicrosoftPartner: MicrosoftPartner: Microsoft

   Partner

   on Oct 11, 2023
3. github-actions commented on Oct 11, 2023

   

   github-actionsbot

   on Oct 11, 2023

   More actions

   ⚠️	Missing Reproducible Example
   ℹ️	We could not detect a reproducible example in your issue report. Please provide either: If your bug is UI related: a Snack If your bug is build/update related: use our Reproducer Template. A reproducer needs to be in a GitHub repository under your username.
4. github-actions

   added

   Needs: ReproThis issue could be improved with a clear list of steps to reproduce the issue.This issue could be improved with a clear list of steps to reproduce the issue.

   on Oct 11, 2023
5. Jore commented on Oct 12, 2023

   

   Jore

   on Oct 12, 2023

   More actions

   Yeah, I'm having the same issue. :(
6. robhogan commented on Oct 12, 2023

   

   robhogan

   on Oct 12, 2023

   Collaborator

   More actions

   Thanks for reporting - we're about to publish an update to normalize-colors removing the Node 18 restriction, and tighten the transitive dependency via react-native-deprecated-prop-types.

   Workaround

   As a mitigation, you can init the project using Node 18, add a resolutions field to your package.json, and then drop back to Node 16.

   nvm use 18
   npx --yes react-native@0.72.5 init testcli72 --template react-native@0.72.5 --skip-install
   cd testcli72

   Add to your new package.json as a top-level field (docs: resolutions):

   "resolutions": {
     "@react-native/normalize-colors": "^0.72.0"
   },

   nvm use 16
   yarn install
   yarn start

   👍React with 👍1Reacted by Nicola Corti

   🎉React with 🎉1Reacted by Tri Lam

   🚀React with 🚀1Reacted by Tri Lam
7. kelset

   pinned this issue on Oct 12, 2023
8. cortinico

   added

   Impact: RegressionDescribes a behavior that used to work on a prior release, but stopped working recently.Describes a behavior that used to work on a prior release, but stopped working recently.

   Needs: React Native Team Attention

   and removed

   Needs: Triage 🔍

   Needs: ReproThis issue could be improved with a clear list of steps to reproduce the issue.This issue could be improved with a clear list of steps to reproduce the issue.

   on Oct 12, 2023
9. huntie commented on Oct 12, 2023

   

   huntie

   on Oct 12, 2023

   Last edited by huntie

   Collaborator

   More actions

   Resolved — please retry creating new React Native projects

   We've just published @react-native/normalize-colors@0.74.1, which removes the Node 18 constraint and should resolve this issue.

   • Please retry npx react-native init from now, and it should work.
   • In existing recently created projects, you should be able to remove the "resolutions" workaround (and/or delete yarn.lock and reinstall).

   We're sorry this issue happened! Thanks @robhogan for actioning changes. We're following up with a more durable fix to eliminate the "*" version specifier from the dependency tree — which will prevent future changes impacting current React Native versions.

   👍React with 👍1Reacted by Vivek Gautam
10. huntie

    closed this as completedon Oct 12, 2023
11. cortinico

    changed the title [-]Unable to create new RN 0.72 project with Node 16 again[/-] [+][FIXED] Unable to create new RN 0.72 project with Node 16 again[/+] on Oct 12, 2023
12. cortinico

    added

    Resolution: FixedA PR that fixes this issue has been merged.A PR that fixes this issue has been merged.

    on Oct 12, 2023
13. facebook-github-bot

    added a commit that references this issue on Oct 14, 2023

    Verdaccio: proxy `@react-native/normalize-colors` from NPM (#40971)

    ...

    d282ebe
14. NickGerleman

    unpinned this issue on Oct 27, 2023