[Bug] `yarn set version berry` writes absolute (non-portable) path into .yarnrc.yml
See original GitHub issue- I’d be willing to implement a fix
Describe the bug
yarn set version berry
writes a .yarnrc.yml
with an absolute path for yarnPath
. I assume this is a bug since the .yarnrc.yml
and .yarn/releases
are meant to be portable and local.
To Reproduce
I created a reproduction with Github Actions that can also be copy-pasted to run locally. https://github.com/cspotcode/repros/tree/yarnrc-absolute-yarnPath
Environment if relevant (please complete the following information):
- OS: Ubuntu
- Node version v12.15.0
- Yarn version 2.0.0-rc.28
Issue Analytics
- State:
- Created 4 years ago
- Reactions:18
- Comments:16 (3 by maintainers)
Top Results From Across the Web
Configuration options | Yarn - Package Manager
List of all the configuration option for Yarn (yarnrc files)
Read more >Repository - GitLab
An error occurred while loading commit signatures ... yarn-berry.cjs ... prefer setting npmRegistryServer in your .yarnrc.yml file" ...
Read more >Can't find module yarn-3.x.x.cjs (Yarn v3) - Stack Overflow
I set my yarn version (in yarnrc.yml) to the default yarn (I used homebrew) yarnPath ...
Read more >Configuration.ts | searchcode
/packages/yarnpkg-core/sources/Configuration.ts ... accept actual paths must end with the "Filename" suffix 119// prefer to use absolute paths instead, ...
Read more >.yarn/releases/yarn-2.2.2.cjs ...
Usage({description:"get the path to a binary script",details:"\n When used ... prefer setting npmRegistryServer in your .yarnrc.yml file" ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Same –
yarn set version berry
yarn set version berry
It seems like the work around is to run
yarn set version berry
twice in a row, until they update the global yarn install version.A fix seems to have been merged into the 1.x repo: https://github.com/yarnpkg/yarn/pull/7931