Open chtnnh opened 3 years ago
Update: I tried removing the outdated package-lock.json
and running npm i
which led to the following error:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: graphqurl-graphiql@0.2.0
npm ERR! Found: react-redux@5.1.2
npm ERR! node_modules/react-redux
npm ERR! react-redux@"^5.0.6" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react-redux@"^3.0.0 || ^4.0.0" from multireducer@1.0.2
npm ERR! node_modules/multireducer
npm ERR! multireducer@"^1.0.2" 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/chtnnh/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/chtnnh/.npm/_logs/2021-10-26T17_26_29_274Z-debug.log
Do any of the project maintainers/contributors think I should file this as a separate issue?
Isn't package.lock supposed to have the required versions of dependencies for running it?
Afaik, that information is stored in the package.json and not package.lock
For locking the versions? I think they left it on purpose. I'm not able to build it either though lmao
I am trying to fix #23 but I am unable to proceed as my attempts at installing
graphql-voyager
are hampered with this error.