My situation is this:
I had a working copy of a react-native project that was working well. Had it commited to my git repository.
I decided to upgrade react-native to 0.26.3 and then 0.28 and finally ended up in a big dependency mess with collisions. So decided to go back to previous working version. Reverted the changes. Removed node_modules folder from my working directory.
But now npm install
just won't work.
My working dependencies in package.json
"dependencies": {
"immutable": "^3.8.1",
"key-mirror": "^1.0.1",
"react": "^15.0.2",
"react-native": "^0.26.0",
"react-native-router-flux": "^3.26.1",
"react-redux": "^4.4.5",
"redux": "^3.5.2",
"redux-thunk": "^2.1.0",
"strformat": "0.0.7"
},
"devDependencies": {
"babel-core": "^6.10.4",
"babel-jest": "^12.1.0",
"babel-preset-es2015": "^6.9.0",
"babel-preset-react-native": "^1.9.0",
"babel-register": "^6.9.0",
"chai": "^3.5.0",
"fetch-mock": "^4.5.4",
"jest-cli": "^12.1.1",
"mocha": "^2.5.3",
"mockery": "^1.7.0",
"nock": "^8.0.0",
"redux-mock-store": "^1.1.1",
"sinon": "^1.17.4",
"sinon-chai": "^2.8.0",
"sinon-stub-promise": "^2.0.0"
}
Now I get
npm ERR! peerinvalid The package react@15.1.0 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer react-native@0.26.3 wants react@15.0.2
npm ERR! peerinvalid Peer react-redux@4.4.5 wants react@^0.14.0 || ^15.0.0-0
This just not makes sense to me, as my react dependency is 15.0.2 and react-native 0.26.0 as you can see in package.json.
Note that this is from a previous commit that was working (the whole lot). I also did a npm ls
. Weirdly wrong dependencies are shown in the tree like wrong versions of react-native
, react-native-router-flux
, react
.
For existing projects if you want to install/downgrade to lower version
npm install react-native@x.x.x ex: npm install react-native@0.43.4
This will install the version specified.
Check the installed version react-native -version
Please update your react
dependency in package.json to explicitly be 15.0.2
, not ^15.0.2
since the latter resolves to 15.1.0
which causes this issue. It is recommended to leave it that way until you upgrade for the next time and get this error once again (to avoid react
changing its version in the meantime and react-native
not being ready for it).
Also, with npm3 EPEERINVALID
is no longer an error, but warning.
Just run
npm install react-native@0.43.8
Replace 0.43.8
with version you need.
Try npm prune
and then npm i
again.
The command npm prune
will basically remove all unwanted packages, and npm i
will make sure all missing packages are installed.
Downgrading React Native requires manual steps. I recommend using https://github.com/react-native-community/rn-diff-purge/compare/ . here are my steps
yarn
or npm install
Important: If you're downgrading multiple versions then you should downgrade one version at a time. For example, downgrading from 0.61.x to 0.58.x, should towngrade to version 0.60.x first, test that it works in iOS and Android then move on and downgrade to version 0.59.x
如果您使用react-native,则可以使用所需的版本修改package.json文件,然后删除所有节点模块rm -rf node_modules,然后重新安装npm install
If you change the version in Package.json
and reinstall npm packages
it will make build errors . Please refer and downgrade/upgrade to a specific version.
I tried to downgrade from react-native 0.71.1
to 0.70.4
with just npm i react-native@0.70.4
and fix whatever errors came up. In my case I needed this because the package react-native-vision-camera
was not yet compatible with react-native 0.71.1.
But I had dozens of errors, which after I while I started to understand are due to the fact that the whole android folder that is being set up from a template when you run the npx react-native init
script, has differences and must match the react-native package version. So I guess if you downgrade a minor version in this way, not just a patch, you are just very lucky if it works somehow. I would not do it.
I instead decided to freshly init react-native with the desired version:
Just git commit all your changes and push them to the remote (to be safe), mv
your current project folder to a different name.
Run npx react-native init <YourProjectName> --version 0.70.6
to get the desired version, but make sure to use the same ProjectName, otherwise you might have configuration mismatches.
Integrate your own code from the old project folder (if you forget something git will tell you later), merge configuration files, etc.
add packages by running npm install <package-name> <package-2-name> <etc.)
and npm install -D
(for devDependencies). Don't copy the dependencies / devDependencies over from package.json, as that way you'll probably not get the right package versions that match your versions of react, react-native etc.
finally copy .git
folder from your old project folder into the new one, and check the changes, to make sure you did not forget anything. And then you will actually see all the differences in the template I mentioned above. In my case more than 30 files were different between those minor versions.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.