I was just trying out a new IHP Backend project based on the expo template. When I check out the templated project and run npm install
I'm getting this error:
[nix-shell:~/pymodules/attics-mobile]$ npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: ihp-backend-expo-starter@1.0.0
npm ERR! Found: react@17.0.1
npm ERR! node_modules/react
npm ERR! react@"17.0.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^17.0.2" from ihp-backend@0.1.0
npm ERR! node_modules/ihp-backend
npm ERR! ihp-backend@"*" from the root project
Does this require an upstream PR to the template to bump the react version?
I also had a question about which npm version to use. I've check the project out into a separate repo but would like to integrate it with an existing IHP app. I'm wondering what the best way to ensure that I use a consistent npm version pinned to the same nixpkgs set is?
Thanks!
Just updated the package via https://github.com/digitallyinduced/ihp-backend-expo-starter/commit/81ad1d1a1777452236a6a94180272c9166ed52d2
Can you try out again?
For integrating it into an existing IHP app, I'd suggest to use DataSync directly.
You can include it inside the package.json like this:
The last part of the
https://gitpkg.now.sh/digitallyinduced/ihp/lib/IHP/DataSync?3b66d8db44a69a2d58c7b47f18996ce1a74f38bc
url is the commit hash of the IHP repo itself. If you set that to your project's commit hash, you should have a consistent version