Closed Mikaela closed 3 months ago
Additionally it's not necessary to call corepack
constantly since corepack enable
should make yarn
point to it, but I am choosing the lazy way out of having to figure out how to get the CI to use corepack version instead of Yarn Classic which is installed by default.
It's inspired by https://github.com/nodejs/corepack/blob/v0.28.2/README.md#corepack-enable--name
Scimming through the CI logs it seems that it's unable to find Draupnir version, which I think is related to this
I think that needs actual coder to check it thogh.
Yeah that's a known issue and unrelated to this PR, don't worry about it
@Mikaela did you follow https://yarnpkg.com/migration/guide ?
More or less, although by accident
oki
Been playing around with yarn4 just to make sure everything is in order, unfortunately I haven't been able to get yarn link
working with VSCode's debugger when linking MPS locally. And that seems to be because they no longer use a symlink in node_modules
.
https://classic.yarnpkg.com/lang/en/docs/cli/link/ https://yarnpkg.com/cli/link https://yarnpkg.com/configuration/manifest#resolutions https://yarnpkg.com/protocol/portal
I'm investigating this but it might take awhile.
Ok, that looks promising. However, seems like projects that have been touched by yarn classic aren't automatically migrated to use "yarn plug'n'play" which is required for the editor integration. https://yarnpkg.com/migration/pnp. And that migration guide requires some major work.
Briefly talked on Matrix, I think the project was previously using an old yarn version since there was a warning about the project being updated to new yarn version when I ran
corepack use yarn
.I don't know if this brings breaking changes and I am curious on whether the tests or CI pass.