-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
npm install fails with react 17.0.1 and react-native 0.64.0 #2603
Comments
Couldn't find version numbers for the following packages in the issue:
Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3. |
Couldn't find version numbers for the following packages in the issue:
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:
Can you verify that the issue still exists after upgrading to the latest versions of these packages? |
Couldn't find version numbers for the following packages in the issue:
Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3. |
+1 unable to install |
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? |
use yarn it will resolve many issues. |
Very odd, I've just installed paper after creating a fresh project with typescript template. |
Using: When trying to install dependencies (by using npm install) i'm getting: 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. |
Having this problem as well on a fresh new react-native ts template when using npm. "react": "17.0.1" I used yarn instead and it worked. |
For those using npm 7, for now, these options seem to work
Original answer on stackoverflow: https://stackoverflow.com/a/65568080 |
tldr: looks like this is a bug in NPM not an issue with I think this issue isn't specific to It appears to be caused by (a bug in?) NPM 7's new strictness in handling peer dependencies:
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:
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 |
i was having same issue with npm $ npm i react-native-paper npm ERR! A complete log of this run can be found in: |
for NPM v7 use
or use yarn. |
+1 same error. Are you sure running the command with --force doesn't break things |
not work for me |
@RishabhKarnad Thanks,It works for me. |
try yarn!
it worked for me. |
|
Thank you mate this works for me on
|
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 My error is consistently:
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 |
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 |
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. |
|
I always use this
|
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
The text was updated successfully, but these errors were encountered: