npm install fails with react 17.0.1 and react-native 0.64.0 #2603

Activity

1. github-actions commented on Mar 15, 2021

   

   github-actionsBot

   on Mar 15, 2021

   More actions

   Couldn't find version numbers for the following packages in the issue:

   • react-native-vector-icons
   • npm
   • yarn
   • expo

   Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.
2. github-actions commented on Mar 15, 2021

   

   github-actionsBot

   on Mar 15, 2021

   More actions

   Couldn't find version numbers for the following packages in the issue:

   • react-native-vector-icons
   • npm
   • expo

   Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

   The versions mentioned in the issue for the following packages differ from the latest versions on npm:

   • yarn (found: 7.6.3, latest: 1.22.10)

   Can you verify that the issue still exists after upgrading to the latest versions of these packages?
3. github-actions commented on Mar 15, 2021

   

   github-actionsBot

   on Mar 15, 2021

   More actions

   Couldn't find version numbers for the following packages in the issue:

   • react-native-vector-icons
   • yarn
   • expo

   Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.
4. hussainahmad commented on Mar 16, 2021

   

   hussainahmad

   on Mar 16, 2021

   More actions

   +1 unable to install react-native-paper with latest react-native.
5. kuasha420 commented on Mar 17, 2021

   

   kuasha420

   on Mar 17, 2021

   More actions

   Yarn can install react native paper on a freshly generated RN64 Project .
6. geovrisco commented on Mar 18, 2021

   

   geovrisco

   on Mar 18, 2021

   More actions

   Yarn can install react native paper on a freshly generated RN64 Project .

   im using npm but get the same error, any workaround for this particular issue?
7. raajnadar commented on Mar 18, 2021

   

   raajnadar

   on Mar 18, 2021

   Collaborator

   More actions

   use yarn it will resolve many issues.

   👍React with 👍9Reacted by Justin Latimore, ice-hector, Yosef S Adelman, Raj , itxhamzajaved, Osama Ahmed, prakharINF, Salvatore Manna and Alauddin Ahmed

   👎React with 👎104Reacted by Manu, Nik Khilnani, mbalc, keithgoodwin, Ihor, Roberto Wesley Overdijk, Rasmey SARETH, Edson Dos Santos, Stefan Morcodeanu, DSJS and 94 more

   😄React with 😄1Reacted by Misha

   😕React with 😕1Reacted by Oliver Lopez
8. kuasha420 commented on Mar 18, 2021

   

   kuasha420

   on Mar 18, 2021

   More actions

   Very odd, I've just installed paper after creating a fresh project with typescript template.
9. siof commented on Apr 1, 2021

   

   siof

   on Apr 1, 2021

   Last edited by siof

   More actions

   Using:
   "react": "17.0.1"
   "react-native": "0.64.0"
   "react-native-paper": "^4.7.2"
   "npm": "^6.14.11"

   When trying to install dependencies (by using npm install) i'm getting:
   @callstack/react-theme-provider@3.0.5 requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.

   react-theme-provider in version 3.0.5 is dependency of react-native-paper in version 4.7.2

   I'm not sure but maybe this mismatch in required versions is causing problem.
10. nalzayat commented on Apr 9, 2021

    

    nalzayat

    on Apr 9, 2021

    Last edited by nalzayat

    More actions

    Having this problem as well on a fresh new react-native ts template when using npm.

    "react": "17.0.1"
    "react-native": "0.64.0"
    "react-native-paper": "^4.7.2"
    "npm": "^7.7.6"

    I used yarn instead and it worked.
11. RishabhKarnad commented on Apr 19, 2021

    

    RishabhKarnad

    on Apr 19, 2021

    Last edited by RishabhKarnad

    More actions

    For those using npm 7, for now, these options seem to work

    • Pass the --legacy-peer-deps flag when using npm commands
    • Downgrade to npm 6 which is less strict with peer dependencies

    Original answer on stackoverflow: https://stackoverflow.com/a/65568080

    👍React with 👍43Reacted by Tiago Barros, Ebrahim, Xavier Carrel, SHANbic, Huthman King, 江辰, Paweł Bęza, Fausto Fusse, 이정인, Muthukrishnan Kandasamy and 33 more

    🎉React with 🎉17Reacted by Ebrahim, Christopher DATO, matheustrindade, Muthukrishnan Kandasamy, Lex , Medkhat, Abdus Salam, Sanju S, Kaabi Taoufik, Aykut Mayali and 7 more

    ❤️React with ❤️9Reacted by Muthukrishnan Kandasamy, Lex , Medkhat, Fredrik, Abdus Salam, Olamide Onakoya, Sanju S, Kaabi Taoufik and Khurram44

    🚀React with 🚀7Reacted by DSJS, Muthukrishnan Kandasamy, Medkhat, Abdus Salam, Sanju S, Kaabi Taoufik and litterboyme

    👀React with 👀3Reacted by Abdus Salam, Kaabi Taoufik and benisdp
12. AlanSl commented on Apr 19, 2021

    

    AlanSl

    on Apr 19, 2021

    Last edited by AlanSl

    More actions

    tldr: looks like this is a bug in NPM not an issue with react-native-paper, try adding --force to your npm install command for now (or use Yarn).

    ---

    I think this issue isn't specific to react-native-paper, I'm getting the same from installing react-navigation.

    It appears to be caused by (a bug in?) NPM 7's new strictness in handling peer dependencies:

    • react-native-paper (and many others) says "I'm happy with any version of react" (peer dep react: "*")
      • NPM7 says "Okay, here's the latest, 17.0.2"
    • react-native-paper (and many others) says "I'm happy with any version of react-native" (peer dep react-native: "*")
      • NPM7 says "Okay, here's the latest, 0.64.0"
    • react-native 0.64.0 says "I specifically want react 17.0.1 please" (peer dep react: "17.0.1", it's 17.0.2 in the next release but that's not out yet)
      • NPM7 says "BUT WE'VE ALREADY INSTALLED 17.0.2! THIS IS A DISASTER" and crashes

    Yarn in the same situation just installs React 17.0.1, and everyone is happy. I'd call this a bug in NPM and it looks like I'm not alone: NPM bug report npm/cli#3083 and PR npm/arborist#266

    In the meantime, this current NPM7 behaviour can be temporarily bypassed by either:

    • Passing --force, which outputs warnings instead of crashing (I'd try this first)
    • Passing --legacy-peer-deps, which doesn't install any missing peer dependencies (like NPM <=6)

    ---

    Update May 2021 - The NPM bug is still there, the above-linked PR failed to fix it, they've opened a new issue npm/cli#3171 so we still need to keeping using --force (or, switch to Yarn).

    👍React with 👍10Reacted by Dror-Bar, FZs, Jeremias Araujo, Colin Cowles, Christopher DATO, Ivan Cézanne Seara, Kumar Gaurav, Ved-evitpl, Daniel T and forandoe
13. bhargav29dev commented on May 4, 2021

    

    bhargav29dev

    on May 4, 2021

    More actions

    i was having same issue with npm

    $ npm i react-native-paper
    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE unable to resolve dependency tree
    npm ERR!
    npm ERR! Found: react@17.0.1
    npm ERR! node_modules/react
    npm ERR! peer react@"17.0.1" from react-native@0.64.0
    npm ERR! node_modules/react-native
    npm ERR! peer react-native@">=0.64.0-rc.0 || 0.0.0-" from @react-native-community/cli@5.0.1-alpha.2
    npm ERR! node_modules/@react-native-community/cli
    npm ERR! @react-native-community/cli@"^5.0.1-alpha.0" from react-native@0.64.0
    npm ERR! react-native@"0.64.0" from the root project
    npm ERR! 1 more (react-native-paper)
    npm ERR! peer react@"^16.0.0 || ^17.0.0" from react-shallow-renderer@16.14.1
    npm ERR! node_modules/react-shallow-renderer
    npm ERR! react-shallow-renderer@"^16.13.1" from react-test-renderer@17.0.1
    npm ERR! node_modules/react-test-renderer
    npm ERR! dev react-test-renderer@"17.0.1" from the root project
    npm ERR! 4 more (react-test-renderer, use-subscription, ...)
    npm ERR!
    npm ERR! Could not resolve dependency:
    npm ERR! peer react@"^16.3.0" from @callstack/react-theme-provider@3.0.5
    npm ERR! node_modules/react-native-paper/node_modules/@callstack/react-theme-provider
    npm ERR! @callstack/react-theme-provider@"^3.0.5" from react-native-paper@4.8.1
    npm ERR! node_modules/react-native-paper
    npm ERR! react-native-paper@"" from the root project
    npm ERR!
    npm ERR! Fix the upstream dependency conflict, or retry
    npm ERR! this command with --force, or --legacy-peer-deps
    npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
    npm ERR!
    npm ERR! See C:\Users\DELL\AppData\Local\npm-cache\eresolve-report.txt for a full report.

    npm ERR! A complete log of this run can be found in:
    npm ERR! C:\Users\DELL\AppData\Local\npm-cache_logs\2021-05-04T12_20_14_663Z-debug.log
14. kuasha420 commented on May 4, 2021

    

    kuasha420

    on May 4, 2021

    More actions

    for NPM v7 use

    npm i --legacy-peer-deps

    or use yarn.

    👍React with 👍3Reacted by Matthew Broadhead, Saurav Mulam and tkostantinov

    🎉React with 🎉1Reacted by tkostantinov
15. hi337 commented on May 15, 2021

    

    hi337

    on May 15, 2021

    More actions

    +1 same error. Are you sure running the command with --force doesn't break things
16. aboodtech commented on May 15, 2021

    

    aboodtech

    on May 15, 2021

    Author

    More actions

    I got it working at the end by uninstalling latest nodeJS version (16x) and made sure my PATH only points at the stable version (14.15.1).

    DONT use latest version of node, instead use the stable (recommended one)

    

    👍React with 👍3Reacted by Samuel Beaulieu, Kevin Coleman and atiq4112
17. chandniKkpl commented on Jul 8, 2021

    

    chandniKkpl

    on Jul 8, 2021

    More actions

    for NPM v7 use

    npm i --legacy-peer-deps

    or use yarn.

    not work for me

    👍React with 👍1Reacted by Aline Matos

    👎React with 👎2Reacted by razavistag and VARUN KUMAR MEDAM
18. xuya227939 commented on Jul 25, 2021

    

    xuya227939

    on Jul 25, 2021

    More actions

    @RishabhKarnad Thanks，It works for me.
19. SaadWaheed10 commented on Aug 1, 2021

    

    SaadWaheed10

    on Aug 1, 2021

    More actions

    Current behaviour

    npm install react-native-paper fails with latest react-native release 0.64.0

    Error is displayed when trying to install react-native-paper using npm

    Expected behaviour

    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE unable to resolve dependency tree
    npm ERR!
    npm ERR! Found: react@17.0.1
    npm ERR! node_modules/react
    npm ERR! peer react@"17.0.1" from react-native@0.64.0
    npm ERR! node_modules/react-native
    npm ERR! peer react-native@">=0.64.0-rc.0 || 0.0.0-" from @react-native-community/cli@5.0.1-alpha.1 npm ERR! node_modules/@react-native-community/cli npm ERR! @react-native-community/cli@"^5.0.1-alpha.0" from react-native@0.64.0 npm ERR! react-native@"0.64.0" from the root project npm ERR! 1 more (react-native-paper) npm ERR! peer react@"^16.0.0 || ^17.0.0" from react-shallow-renderer@16.14.1 npm ERR! node_modules/react-shallow-renderer npm ERR! react-shallow-renderer@"^16.13.1" from react-test-renderer@17.0.1 npm ERR! node_modules/react-test-renderer npm ERR! dev react-test-renderer@"17.0.1" from the root project npm ERR! 4 more (react-test-renderer, use-subscription, ...) npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^16.3.0" from @callstack/react-theme-provider@3.0.5 npm ERR! node_modules/react-native-paper/node_modules/@callstack/react-theme-provider npm ERR! @callstack/react-theme-provider@"^3.0.5" from react-native-paper@4.7.2 npm ERR! node_modules/react-native-paper npm ERR! react-native-paper@"" from the root project
    npm ERR!
    npm ERR! Fix the upstream dependency conflict, or retry
    npm ERR! this command with --force, or --legacy-peer-deps
    npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
    npm ERR!
    npm ERR! See /Users/xx/.npm/eresolve-report.txt for a full report.

    npm ERR! A complete log of this run can be found in:
    npm ERR! /Users/xx/.npm/_logs/2021-03-15T10_46_15_026Z-debug.log

    Code sample

    npx react-native init MyTestApp
    cd MyTestApp && npm install react-native-paper

    Screenshots (if applicable)

    What have you tried

    yarn seems to work fine.

    Your Environment

    software version
    ios or android both
    react-native 0.64.0
    react-native-paper 4.7.2
    node v14.15.1
    npm or yarn npm: 7.6.3
    expo sdk

    try yarn!

    1. yarn install.
    2. yarn add react-native-paper.

    it worked for me.

    👎React with 👎1Reacted by dPowNextdoor
20. Selenestica commented on Aug 4, 2021

    

    Selenestica

    on Aug 4, 2021

    More actions

    npm i --legacy-peer-deps didn't work for me, but
    npm i react-native-paper --force did work.

    🎉React with 🎉2Reacted by VARUN KUMAR MEDAM and Deyky Pinheiro
21. razavistag commented on Aug 19, 2021

    

    razavistag

    on Aug 19, 2021

    More actions

    for NPM v7 use

    npm i --legacy-peer-deps

    or use yarn.

    Thank you mate this works for me on

    "dependencies": { 
        "react": "17.0.2",
        "react-native": "0.65.0"
    },
    

    npm i --legacy-peer-deps
npm install @ant-design/react-native --save

    👍React with 👍3Reacted by razavistag, Arafat Zahan and Ricardo Sánchez
22. kevincoleman commented on Aug 30, 2021

    

    kevincoleman

    on Aug 30, 2021

    Last edited by kevincoleman

    More actions

    I have what I believe is this problem, still. I’m using react 17.0.1 and react native 0.64.2. I’ve tried installing with yarn and with npm. I’ve tried upgrading node to 16.x with npm 7.x and then back to 14.x with npm 6.14.14.

    I’m doing a full rebuild of the project every time, including removing node_modules and lock file(s), doing a full pod install after removing Podfile.lock, clearing bundler cache, and cleaning the build folder before building in xcode. Just no joy.

    My error is consistently:

    error Unable to resolve module fs from /Users/(user)/(project path)/node_modules/firebase-admin/lib/firebase-namespace.js: fs could not be found within the project or in these directories:
      node_modules
    

    Ironically, installing with yarn worked fine for me just yesterday. Perhaps I have another issue and this thread is just a red herring... :(

    Edit:

    Aha! I discovered that there are (weirdly) two ways you can import firebase-admin into react native projects. I guess I was doing import { firestore } from "firebase-admin" and I needed to be doing import firestore from '@react-native-firebase/firestore' So, this was indeed a red herring, but I’ll leave my comment around in case anyone else with my problem finds this thread while looking for a solution. Carry on!
23. lukewalczak

    closed this as completedin #2930on Oct 15, 2021
24. lukewalczak commented on Oct 15, 2021

    

    lukewalczak

    on Oct 15, 2021

    Member

    More actions

    Thanks to the PR the issue should be fixed, however we are planning the release in the upcoming weeks, so in the meantime you can try install from the main branch.

    👍React with 👍1Reacted by Kevin Coleman
25. liskibruh commented on Jul 5, 2022

    

    liskibruh

    on Jul 5, 2022

    Last edited by liskibruh

    More actions

    I had this issue and nothing seemed to work. I fixed it by downgrading node to version 12.14.1 Uninstall the current node version and install 12.14.1 from this link.
26. IsiteYves commented on Aug 3, 2022

    

    IsiteYves

    on Aug 3, 2022

    More actions

    yarn install seems to resolve the issue on my side too!👌

    👍React with 👍1Reacted by Chaitanya Bhat
27. Dat-Mobile commented on Apr 30, 2023

    

    Dat-Mobile

    on Apr 30, 2023

    More actions

    I always use this

    npm i --force