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

[Bug?]: Problem with using workspace:^ in yarn 4.1.0 #6118

Closed
1 task
joeldinis opened this issue Feb 7, 2024 · 0 comments · Fixed by #6205
Closed
1 task

[Bug?]: Problem with using workspace:^ in yarn 4.1.0 #6118

joeldinis opened this issue Feb 7, 2024 · 0 comments · Fixed by #6205
Labels
bug Something isn't working

Comments

@joeldinis
Copy link

Self-service

  • I'd be willing to implement a fix

Describe the bug

Hi. In my development team we were using 3.2.1 yarn.
We decided to upgrade to 4.0.1, and after doing so, I wanted to test installation, so I ran yarn install.
image

after some console.log inspecting, I realized that one of our packages has workspace:^ and that is being thrown by yarn in the line specified by the crash log. I followed the exception to the website and it recommended me to open an issue so here I am. Am doing something wrong? Or is it a bug by yarn? Keep in mind, the same code was working in yarn 3.2.1 before I updated.

image

To reproduce

I guess have the same setup ive shown in package.json

Environment

yarn dlx -q envinfo --preset jest

  System:
    OS: Windows 11 10.0.22621
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12800H
  Binaries:
    Node: 20.11.0 - ~\AppData\Local\Temp\xfs-2c7a4d9f\node.CMD
    Yarn: 4.1.0-git.20240130.hash-943a9f0 - ~\AppData\Local\Temp\xfs-2c7a4d9f\yarn.CMD
    npm: 10.2.4 - ~\.nvm\versions\node\v20.11.0\bin\npm.CMD

i used sources to debug it

Additional context

No response

@joeldinis joeldinis added the bug Something isn't working label Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant