john-ciq
john-ciq
John Ghidiu / interio.io
This dockerfile allowed me to test different versions of yarn in order to find the version at which this new issue presented. It appears to be 1.22.20 ```FROM node:20-alpine ##...
> In that case, the issue is happening because yarn from npm global installs is ahead (or behind? I can't remember exactly how path environment variables work) of corepack's binaries...
Thanks for the help and explanation, @arcanis. I did have to set COREPACK_ROOT as well as SKIP_YARN_COREPACK_CHECK, as per https://github.com/yarnpkg/yarn/blob/1.22-stable/src/cli/index.js#L292C21-L292C33 But all is well now, thank you!
@Aghassi, that situation seems similar to mine. If possible, you may be able to avoid the error by setting _both_ `COREPACK_ROOT=0` and `YARN_SKIP_COREPACK_CHECK=0` (the values won't matter, but the environment...
@Aghassi It does seem like a breaking change, though I can't speak for yarn contributors or maintainers. The solution I came to was to force an install of yarn 1.22.19.
John Ghidiu / interop.io
John Ghidiu / interop.io