[Bug] Adding plugin to .yarnrc.yml causes yarn to use 1.x runtime

[ianschmitz]

• I'd be willing to implement a fix

Describe the bug
Adding a plugins section to .yarnrc.yml forces yarn to use legacy version.

To Reproduce

Transforming this config file:

nodeLinker: node-modules
yarnPath: ".yarn/releases/yarn-berry.js"

to this:

nodeLinker: node-modules
plugins:
    - path: ".yarn/plugins/@yarnpkg/plugin-interactive-tools.js"
      spec: "@yarnpkg/plugin-interactive-tools"
yarnPath: ".yarn/releases/yarn-berry.js"

causes yarn -v to report 1.22.0 instead of 2.0.0-rc.29. The plugin was added using the yarn plugin import interactive-tools command

Environment if relevant (please complete the following information):

• OS: Ubuntu 19.10
• Node version: 10.17.0
• Yarn version: 1.22.0 globally installed

[missing1984]

Encountered the same issue.

Move up yarnPath to the top fixes the problem for me

[ianschmitz]

Thanks @missing1984, that workaround seemed to work for me as well.

[yarnbot]

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolution faster). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label.

[paul-soporan]

Fixed in yarnpkg/yarn#7931.