After migrating to Yarn 2, Webpack wants to install a CLI

[o-alquimista]

Bug description

After installing Yarn 2 as instructed here, and running a Webpack Encore (Symfony) script, Webpack now asks for a CLI. It never did before.

Command

This will build the assets and move them into the public/ directory with Webpack Encore:

yarn encore dev

What is the current behavior?

Webpack is asking me to install webpack-cli. I simply answered 'no'. I don't want to mess things up. For now I'll stick with Yarn 1.

What is the expected behavior?

yarn encore dev should execute successfully, as it still does with Yarn 1.

Steps to Reproduce

1. I have upgraded my project to Yarn 2 as instructed.
2. Then I ran yarn install, which completed successfully; followed by yarn up, which finished immediately without any output.
3. Finally, I ran yarn encore dev.

Environment

• Node Version: v13.9.0
• Yarn v1 Version: 1.22.0
• Yarn v2 Version: 2.0.0-rc.29
• OS and version: Ubuntu 19.10 Eoan x86_64
• Symfony 4.4 LTS project (all dependencies up-to-date)

[arcanis]

This is expected. The Webpack CLI is in webpack-cli, not in webpack.

[merceyz]

Based on the date this was opened it was because of a missing peer dependency fixed in webpack/webpack#11190