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

Issue when installing packages inside studio folder #317

Open
shreyas707 opened this issue Aug 16, 2024 · 2 comments
Open

Issue when installing packages inside studio folder #317

shreyas707 opened this issue Aug 16, 2024 · 2 comments

Comments

@shreyas707
Copy link

Steps to reproduce the error:

  1. Run npm install in the root folder
  2. Run cd studio && npm install

The following error occurs:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @sanity/[email protected]
npm ERR! node_modules/@sanity/icons
npm ERR!   @sanity/icons@"^3.3.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @sanity/icons@"^2.3.1" from [email protected]
npm ERR! node_modules/groqd-playground
npm ERR!   groqd-playground@"^0.0.20" 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!
npm ERR! For a full report see:
npm ERR! /Users/shreyas/.npm/_logs/2024-08-16T04_56_22_979Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /Users/shreyas/.npm/_logs/2024-08-16T04_56_22_979Z-debug-0.log

I ran npm install --force and it fixed the issue temporarily and I'm able to run the project just fine. But don't know if this will cause any issues in the future during development.

@xpek20
Copy link

xpek20 commented Sep 13, 2024

Same issue

@thomasKn
Copy link
Collaborator

thomasKn commented Oct 8, 2024

I removed groqd-playground from the studio; there was a peer dependency issue. It should be fixed now.

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

No branches or pull requests

3 participants