Skip to content
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

Remove package-lock.json or update it to latest npm format #103

Open
chtnnh opened this issue Oct 26, 2021 · 4 comments
Open

Remove package-lock.json or update it to latest npm format #103

chtnnh opened this issue Oct 26, 2021 · 4 comments
Assignees

Comments

@chtnnh
Copy link

chtnnh commented Oct 26, 2021

I am trying to fix #23 but I am unable to proceed as my attempts at installing graphql-voyager are hampered with this error.

@chtnnh
Copy link
Author

chtnnh commented Oct 26, 2021

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?

@1stdevfriend
Copy link

Isn't package.lock supposed to have the required versions of dependencies for running it?

@chtnnh
Copy link
Author

chtnnh commented Mar 7, 2022

Afaik, that information is stored in the package.json and not package.lock

@1stdevfriend
Copy link

image

For locking the versions? I think they left it on purpose. I'm not able to build it either though lmao

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants