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

Does Not Work With Yarn 3 #59

Closed
enchorb opened this issue Oct 12, 2023 · 6 comments
Closed

Does Not Work With Yarn 3 #59

enchorb opened this issue Oct 12, 2023 · 6 comments

Comments

@enchorb
Copy link

enchorb commented Oct 12, 2023

I get this error when attempting to run with Yarn 3 & a NX monorepo.

Target project does not exist: npm:fbemitter@https://github.com/crisp-dev/emitter.git#commit=695f60594bdca0c876e5c232de57702ab3151b6f

@baptistejamin
Copy link
Member

Hello! :)

How are you doing today?

Can you explain with details what are you trying to achieve?

@enchorb
Copy link
Author

enchorb commented Oct 12, 2023

Hi, we have the crisp-api@8.1.0 dependency in our package.json when attempting to start any project ie. nx run-many --target=serve --projects=backend we get the above error. Post upgrading to Yarn 3 this is the only package out of 200+ that throws an error. Everything worked fine on Yarn 1.

@baptistejamin
Copy link
Member

Perfect! Can you please share a screenshot of the error?

I will review that with our team.

@enchorb
Copy link
Author

enchorb commented Oct 12, 2023

Can't screenshot on the work computer - here is the full copied error

>  NX   Failed to process project dependencies with "nx-js-graph-plugin".

   Target project does not exist: npm:fbemitter@https://github.com/crisp-dev/emitter.git#commit=695f60594bdca0c876e5c232de57702ab3151b6f
   
   Because of the error the Nx daemon process has exited. The next Nx command is going to restart the daemon process.
   If the error persists, please run "nx reset".

@tilmann
Copy link

tilmann commented Dec 20, 2023

Seeing the same error
2023 12 20 - 09 29 - Slack - #dev - Huddle@2x

Any update on this @baptistejamin

@baptistejamin
Copy link
Member

Hello!

It should be solved with version 8.2.3

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

No branches or pull requests

3 participants